On Monday 24 November 2003 10:24 pm, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Stefan
=?iso-8859-1
And that is what this thread is about: Secure removal of data from
storage media. There definitely is a difference between RLL (as in
1,7i RLL) and modern PRML drives under this
In message [EMAIL PROTECTED], Wes Peters writes:
If you want an interesting problem to work on, come up with a solution to
the keying problem for disk encryption. It somehow needs to allow
automated, unattended reboots during normal operations but prevent
attackers from compromising the
rmkml wrote:
is the _exit() function safe for a thread ?
my program use vfork() and then execve in a thread context.
The documentation mentions that the process has to call _exit() in case
of failure.
But this _exit() is really safe for the parent thread ?
The behaviour is undefined in the
Thanks a lot for the answer. I will change vfork() with fork().
An another question: in the man page of vfork() it is mentionned that
the fork() function has to use _exit(0) too when something wrong with the
execve() happens!
but in a thread context of my program, the use of _exit() may not be
On Fri, Nov 28, 2003 at 12:43:30PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Wes Peters writes:
If you want an interesting problem to work on, come up with a solution to
the keying problem for disk encryption. It somehow needs to allow
automated, unattended reboots
In message [EMAIL PROTECTED], Wilko Bulte writes:
On Fri, Nov 28, 2003 at 12:43:30PM +0100, Poul-Henning Kamp wrote:
I have already described one solution to this in my GBDE paper at
BSDcon.
...
Now *that* is a DIY project for the dedicated hobbyist :-)
The terminology and principle, is
Soren, while fixing some issues in DFly related to the ATA driver I
found a serious problem in your driver... actually, it appears to be
in ata-ng -stable and -current as well.
The problem is that you are using M_NOWAIT all over the place. M_NOWAIT
allows malloc() to fail
rmkml wrote:
Thanks a lot for the answer. I will change vfork() with fork().
An another question: in the man page of vfork() it is mentionned that
the fork() function has to use _exit(0) too when something wrong with the
execve() happens!
I can see how you might read it this way, but that's
Kris Kirby [EMAIL PROTECTED] writes:
FreeBSD (4.9-RC) doesn't appear to export schg flags over NFS.
File flags are BSD-specific and are not supported in the NFS protocol.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing
All right, here's an example patch. This patch is against the old
ATA code in DragonFly but most of the issues are the same with the
ATA code in -STABLE and -CURRENT. It does not fix all the problems
(which would be a waste since we are about to import ATAng and do not
want
sadly, all ktrace shows is ktrace launching vmware (from 'ktrace vmware',
shows sh reading and executing, and then ends with the vmware fork).
why not to `ktrace` vmware binary '/usr/local/lib/vmware/bin/vmware'
instead of the shell-script 'vmware'?
28.11.2003; 23:00:47
[SorAlx]
11 matches
Mail list logo