On Thu, Nov 19, 2009 at 07:38:18AM +, xorquew...@googlemail.com wrote:
On 2009-11-18 23:19:14, Julian Elischer wrote:
Wine is an exceptional bit of software, in many ways.
One way it is exceptional is that it uses the system in a number of
ways that nothing else does. For example it
On 2009-11-19 11:03:41, Kostik Belousov wrote:
You forgot to note the version of the kernel you use.
I'm using 7.2-RELEASE-p4 here.
xw
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
On Thu, Nov 19, 2009 at 09:22:14AM +, xorquew...@googlemail.com wrote:
On 2009-11-19 11:03:41, Kostik Belousov wrote:
You forgot to note the version of the kernel you use.
I'm using 7.2-RELEASE-p4 here.
Required syscalls only implemented in 8/HEAD.
pgprTLunyoRuu.pgp
Description:
On 2009-11-19 11:25:48, Kostik Belousov wrote:
I'm using 7.2-RELEASE-p4 here.
Required syscalls only implemented in 8/HEAD.
Ah, thanks.
I assume they won't have made it into 8.0-RELEASE when it shows up?
xw
___
freebsd-hackers@freebsd.org mailing
Greetings,
this little C program (which is actual a minimum excerpt from
sysutils/e2fsprogs) fails to compile on - among others - 8.0-PRERELEASE:
$ cat fail.c
#define _XOPEN_SOURCE 600
#include sys/file.h
$ gcc -W -Wall -O -c fail.c
In file included from fail.c:2:
On Thu, Nov 19, 2009 at 09:36:54AM +, xorquew...@googlemail.com wrote:
On 2009-11-19 11:25:48, Kostik Belousov wrote:
I'm using 7.2-RELEASE-p4 here.
Required syscalls only implemented in 8/HEAD.
Ah, thanks.
I assume they won't have made it into 8.0-RELEASE when it shows up?
It
On 2009-11-19 12:15:18, Kostik Belousov wrote:
On Thu, Nov 19, 2009 at 09:36:54AM +, xorquew...@googlemail.com wrote:
It is in 8.0.
Excellent, thanks.
___
freebsd-hackers@freebsd.org mailing list
Dear all,
I've looked but not found (and I hope I'm in the right group here): Is
there a way to get the user time and system time of a /running/ child
from its parent (without having to mount procfs)? As far as I was able
to tell, I can get the total of user and system time using
kvm_getprocs,
, [Jung-uk Kim wrote:]
| On Wednesday 18 November 2009 01:52 pm, Robert Watson wrote:
| On Tue, 17 Nov 2009, Sharad Chandra wrote:
| Is it known bug or is there any workaround? How will a userland
| process make sure that process will not crash as malloc(3) can
| allocate where ever it
On 19 Nov 2009, at 10:57, Sharad Chandra wrote:
Thanks everyone. mmap(2) worked and program did not crash. Only problem with
it I use only fraction of allocated memory (each request alocate minimum of
one page and my request is in hundreds), rest is waste of it so no one else
will get
Matthias Andree matthias.and...@gmx.de writes:
I've talked to Theodore Y. Ts'o, who is the sysutils/e2fsprogs
upstream maintainer and proposed to remove the _XOPEN_SOURCE
definition (my idea was that the code shouldn't be claiming standards
compliance while it uses non-standard headers), but
Koffie Yahoo koffieya...@gmail.com writes:
I've looked but not found (and I hope I'm in the right group here): Is
there a way to get the user time and system time of a /running/ child
from its parent (without having to mount procfs)?
If you have only one child, there's getrusage(2).
DES
--
xorquew...@googlemail.com wrote:
On 2009-11-18 23:19:14, Julian Elischer wrote:
Wine is an exceptional bit of software, in many ways.
One way it is exceptional is that it uses the system in a number of
ways that nothing else does. For example it sets various special
segment register settings
Sharad Chandra wrote:
, [Jung-uk Kim wrote:]
| On Wednesday 18 November 2009 01:52 pm, Robert Watson wrote:
| On Tue, 17 Nov 2009, Sharad Chandra wrote:
| Is it known bug or is there any workaround? How will a userland
| process make sure that process will not crash as malloc(3) can
|
On Thu, Nov 19, 2009 at 06:27:18AM -0800, Julian Elischer wrote:
xorquew...@googlemail.com wrote:
On 2009-11-18 23:19:14, Julian Elischer wrote:
Wine is an exceptional bit of software, in many ways.
One way it is exceptional is that it uses the system in a number of
ways that nothing else
I've looked but not found (and I hope I'm in the right group here): Is
there a way to get the user time and system time of a /running/ child
from its parent (without having to mount procfs)?
If you have only one child, there's getrusage(2).
Unfortunately, that only works for children that
Koffie Yahoo koffieya...@gmail.com writes:
Unfortunately, that only works for children that have terminated, not
for active children. I'm interested in active children.
Hmm, we could probably add a ptrace(2) operation, but ptrace(2) is
inherently evil.
DES
--
Dag-Erling Smørgrav - d...@des.no
Koffie Yahoo wrote:
I've looked but not found (and I hope I'm in the right group here): Is
there a way to get the user time and system time of a /running/ child
from its parent (without having to mount procfs)?
If you have only one child, there's getrusage(2).
Unfortunately, that
Boris Kochergin sp...@acm.poly.edu writes:
It's not as portable as getrusage(2), but you could probably get the
information you want using libkvm's kvm_getprocs(3) function. The
information available is defined in the kinfo_proc structure in
/usr/include/sys/user.h.
Read the original post.
It's not as portable as getrusage(2), but you could probably get the
information you want using libkvm's kvm_getprocs(3) function. The
information available is defined in the kinfo_proc structure in
/usr/include/sys/user.h.
Unfortunately, as far as I can see the kinfo_proc structure only
I'm looking into using self-encrypting hard drives (TCG Opal standard) with
FreeBSD. In particular I want to use the auto-lock mode. I can't seem to
find the details regarding how the authentication key is provided to the
drive, and where there is any support in FreeBSD to enable unlocking the
In the last episode (Nov 19), Koffie Yahoo said:
It's not as portable as getrusage(2), but you could probably get the
information you want using libkvm's kvm_getprocs(3) function. The
information available is defined in the kinfo_proc structure in
/usr/include/sys/user.h.
Unfortunately,
That's it! Thanks! Problem solved :-)
Jay
On Thu, Nov 19, 2009 at 5:34 PM, Dan Nelson dnel...@allantgroup.com wrote:
In the last episode (Nov 19), Koffie Yahoo said:
It's not as portable as getrusage(2), but you could probably get the
information you want using libkvm's kvm_getprocs(3)
On Thu, Nov 19, 2009 at 12:57 AM, xorquew...@googlemail.com wrote:
Hello.
I've done a lot of reading on this problem and don't understand why what I
have
doesn't work.
http://wiki.freebsd.org/Wine
I have an entirely 32 bit jail, created by cross-compiling the world with
TARGET=i386
On 2009-11-19 17:12:19, Sam Fourman Jr. wrote:
I would like to help get this working.. is there a howto somewhere to
setup a i386 jail on amd64?
I used teh instructions on http://wiki.freebsd.org/Wine (and pointed
the jail to /compat/i386)
Inside teh jail uname -a still produces this:
25 matches
Mail list logo
