Hello hackers,
I'm looking through the Clang Analyzer scans on
http://scan.freebsd.your.org/freebsd-head looking for false positives to report
back to LLVM. There are quite a list of reports suggesting to change vfork()
calls to posix_spawn(). Example from /bin/rpc:
On 14/09/2012 09:49, Erik Cederstrand wrote:
Hello hackers,
I'm looking through the Clang Analyzer scans on
http://scan.freebsd.your.org/freebsd-head looking for false positives to
report back to LLVM. There are quite a list of reports suggesting to change
vfork() calls to posix_spawn().
Den 14/09/2012 kl. 13.03 skrev Ivan Voras ivo...@freebsd.org:
On 14/09/2012 09:49, Erik Cederstrand wrote:
Hello hackers,
I'm looking through the Clang Analyzer scans on
http://scan.freebsd.your.org/freebsd-head looking for false positives to
report back to LLVM. There are quite a list
Hi Mark,
Here's the output of our VMs running on ESXi 4.1u1
FreeBSD 7.4:
# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-100)
# sysctl kern.timecounter.hardware
kern.timecounter.hardware: ACPI-safe
FreeBSD 8.3:
# sysctl
On Fri, Sep 14, 2012 at 4:45 AM, Erik Cederstrand e...@cederstrand.dk wrote:
Den 14/09/2012 kl. 13.03 skrev Ivan Voras ivo...@freebsd.org:
On 14/09/2012 09:49, Erik Cederstrand wrote:
Hello hackers,
I'm looking through the Clang Analyzer scans on
http://scan.freebsd.your.org/freebsd-head
Are errors in /var/log/messages?
I think, you ran out of memory.
With top you can see, how many swap is avaible.
On 09/14/12 07:32, Vijay Singh wrote:
Need some expert help. I have a system that is hung hard, and I was
able to get it into gdb. From show_vmstat I see:
(kgdb-amd64-7.4-95)
On Fri, Sep 14, 2012 at 01:45:49PM +0200, Erik Cederstrand wrote:
Den 14/09/2012 kl. 13.03 skrev Ivan Voras ivo...@freebsd.org:
On 14/09/2012 09:49, Erik Cederstrand wrote:
I'm looking through the Clang Analyzer scans on
http://scan.freebsd.your.org/freebsd-head looking for false
I am trying to change the active partition in MBR.
This should be a matter of changing only two bits (clearing one in one
byte and setting another one in another byte).
However, fdisk complains:
fdisk: Failed to write MBR. Try to use gpart(8).
truss reveals that fdisk failed to open the root
On Fri, Sep 14, 2012 at 5:19 PM, Yuri y...@rawbw.com wrote:
I am trying to change the active partition in MBR.
This should be a matter of changing only two bits (clearing one in one byte
and setting another one in another byte).
However, fdisk complains:
fdisk: Failed to write MBR. Try to
On Sep 14, 2012, at 8:48 AM, Mark Felder f...@feld.me wrote:
Hi Mark,
Here's the output of our VMs running on ESXi 4.1u1
FreeBSD 7.4:
# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-100)
# sysctl kern.timecounter.hardware
On Fri, 14 Sep 2012, Yuri wrote:
I am trying to change the active partition in MBR.
This should be a matter of changing only two bits (clearing one in one byte
and setting another one in another byte).
However, fdisk complains:
fdisk: Failed to write MBR. Try to use gpart(8).
truss reveals
On 09/14/2012 19:23, Warren Block wrote:
Did you actually try gpart? GEOM prevents writes to providers that
are in use, but gpart should handle it correctly if the problem is
just that fdisk doesn't understand GEOM.
# gpart set -a active -i 1 ada0
If that fails, the provider is in use,
12 matches
Mail list logo