On Wed, Jan 25, 2012 at 11:54:46PM +0100, Jilles Tjoelker wrote:
> [snip]
> x micro-vfork-timings1-n
> + micro-vfork-timings1-y
> +--+
> |+
> |
>
Here is a new version of the vfork patch. The concept is the same,
trying to use vfork in simple common cases. Compared to
http://lists.freebsd.org/pipermail/freebsd-hackers/2011-June/035618.html
I have extended vfork use to some command substitutions and allowed
setting an environment variable SH_
On 1/25/12 10:44 AM, Matthias Zitzen wrote:
Hello list,
does anybody have an idea, how to obtain the new name of a renamed file after
the note_rename event is fired. I'm not very familiar with
filesystem-operations. I checked the typical functions like stat or lstat, but
these functions are w
Hi,
On Wed, Jan 25, 2012 at 3:22 PM, Mark Linimon wrote:
> On Wed, Jan 25, 2012 at 03:58:41AM -0500, Arnaud Lacombe wrote:
>> > You seem to be obsessed by picking over
>> > semantics and finding shortcomings to be aggreived over.
>> >
>> Semantics and proper, independent, API are crucial.
>
> I'm
On Wed, Jan 25, 2012 at 03:58:41AM -0500, Arnaud Lacombe wrote:
> > You seem to be obsessed by picking over
> > semantics and finding shortcomings to be aggreived over.
> >
> Semantics and proper, independent, API are crucial.
I'm talking about the semantics of the non-technical part: the wording
Hello list,
does anybody have an idea, how to obtain the new name of a renamed file after
the note_rename event is fired. I'm not very familiar with
filesystem-operations. I checked the typical functions like stat or lstat, but
these functions are working only with filenames.
Matthias
__
On Jan 25, 2012, at 4:50 AM, Dimitry Andric wrote:
> On 2012-01-23 19:46, Ed Maste wrote:
> ...
>> Do you have the reproduction steps documented somewhere (and if not, can
>> you write them up)? In order to have working automated installs we need
>> to be able to unconditionally reinit a drive
> I might just be also interested to review/comment code, discuss
> regressions, and architecture, for a change ;-)
> Unfortunately, such threads rarely ever happen. Most of the time, the
> only food provided is a really indigestible +5000/-3000 patch, where
> all the thinking, architectural design
On 2012-01-23 19:46, Ed Maste wrote:
...
Do you have the reproduction steps documented somewhere (and if not, can
you write them up)? In order to have working automated installs we need
to be able to unconditionally reinit a drive w/o having behavoiur depend
on what happens to be left behind.
On Wed, Jan 25, 2012 at 11:52:02AM +0100, Damien Fleuriot wrote:
> On 1/25/12 11:44 AM, Edward Tomasz Napierała wrote:
> > Patch below changes the way mdconfig(8) parses its arguments:
> > it removes the ordering requirement and makes error messages
> > more descriptive; it also makes the code more
On 1/25/12 11:44 AM, Edward Tomasz Napierała wrote:
> Patch below changes the way mdconfig(8) parses its arguments:
> it removes the ordering requirement and makes error messages
> more descriptive; it also makes the code more readable by
> getting rid of the 'cmdline' variable.
>
> Now, the mdcon
Patch below changes the way mdconfig(8) parses its arguments:
it removes the ordering requirement and makes error messages
more descriptive; it also makes the code more readable by
getting rid of the 'cmdline' variable.
Now, the mdconfig(8) syntax is somewhat weird, and I'm not sure
I tested all t
On Wed, Jan 25, 2012 at 9:58 AM, Arnaud Lacombe wrote:
> Hi,
>
> On Wed, Jan 25, 2012 at 2:28 AM, Mark Linimon wrote:
>>> I might just be also interested to review/comment code, discuss
>>> regressions, and architecture, for a change ;-)
>>> Unfortunately, such threads rarely ever happen. Most of
Hi,
On Wed, Jan 25, 2012 at 2:28 AM, Mark Linimon wrote:
>> I might just be also interested to review/comment code, discuss
>> regressions, and architecture, for a change ;-)
>> Unfortunately, such threads rarely ever happen. Most of the time, the
>> only food provided is a really indigestible +5
14 matches
Mail list logo
