> Hello,
>
> avg@ suggested to include compiler version in the kernel so that it's
> present in uname (and one can easly tell what was used to compile it).
>
> Here is my attempt:
> http://people.freebsd.org/~mjg/patches/newvers-compiler.diff
>
> Basically adds compiler name and version/revision
Andre, do you think the variable "realmem" could be exported as
something like kmemsize or something?
Or maybe a function call to subr_param.c?
The reason I ask is that I would like to scale things like number of
default sysv semaphores to something like 64 per 1GB of "realmem".
Thoughts?
T
good idea.
show version cmd in postgresql prints os version,compiler info etc. useful
for problem report.
jov
在 2012-11-14 上午7:43，"Mateusz Guzik" 写道：
> Hello,
>
> avg@ suggested to include compiler version in the kernel so that it's
> present in uname (and one can easly tell what was used to comp
Hi,
On Wed, 14 Nov 2012 00:43:03 +0100
Mateusz Guzik wrote:
> Hello,
>
> avg@ suggested to include compiler version in the kernel so that it's
> present in uname (and one can easly tell what was used to compile it).
>
> Here is my attempt:
> http://people.freebsd.org/~mjg/patches/newvers-compi
On Wed, Nov 14, 2012 at 12:43:03AM +0100, Mateusz Guzik wrote:
> Hello,
>
> avg@ suggested to include compiler version in the kernel so that it's
> present in uname (and one can easly tell what was used to compile it).
>
> Here is my attempt:
> http://people.freebsd.org/~mjg/patches/newvers-compi
Can anyone comment on current built with clang as default compiler and
ports? Are there any major problems, programs that don't run? Specifically, I am
interested in how Gnome and Xorg (Gnome and Xorg built with default
system gcc) work on world built with clang.
I believe the work around f
Hello,
avg@ suggested to include compiler version in the kernel so that it's
present in uname (and one can easly tell what was used to compile it).
Here is my attempt:
http://people.freebsd.org/~mjg/patches/newvers-compiler.diff
Basically adds compiler name and version/revision after revision of
On Sat, Nov 10, 2012 at 05:46:21PM +1100, Greg 'groggy' Lehey wrote:
> On Friday, 9 November 2012 at 13:52:24 +0100, Dimitry Andric wrote:
> > Looks like yet another cpp -traditional abuse.
>
> Use or abuse? In any case, it's not the only one. In the Good Old
> Days people did things like that.
On Tuesday, 13 November 2012 at 9:11:21 +0200, Alexander Yerenkow wrote:
> Hello there!
> I sometimes see in this list such mails:
> "I got problem with rXX"
> "It's known, it's fixed in rYY".
>
> Sometimes it's my problem, sometimes it's problem of other peoples.
>
> How about make simple
What about cases when something is broken, but not for everybody?
If only GENERIC build, how does that differ from existing tinderboxing?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Simple-check-if-current-is-broken-tp5760481p5760700.html
Sent from the freebsd-current
Today I booted r242670 from the console and noticed an error. This
is one line from the end of dmesg:
ipfw: ipfw_install_state: Too many dynamic rules
The ruleset has always been dynamic and has no additional rules.
Search engines produced similar error messages, but no information
that seems
On 13/11/2012 03:23, Dan Nelson wrote:
> In the last episode (Nov 12), Darrel said:
>> Hello,
>>
>> Today I booted r242670 from the console and noticed an error. This
>> is one line from the end of dmesg:
>>
>> ipfw: ipfw_install_state: Too many dynamic rules
>>
>> The ruleset has always been dyna
On Nov 12, 2012, at 3:50 PM, Glen Barber wrote:
> On Mon, Nov 12, 2012 at 06:11:43PM -0500, Darrel wrote:
>> Hello,
>>
>> Today I booted r242670 from the console and noticed this error message:
>> can't open '/boot/menusets.4th': no such file of directory
>>
>> Error while including /boot/menu
13 matches
Mail list logo
