On Mon, Feb 22, 2010 at 08:47:57PM -0800, Tim Kientzle wrote:
> Juergen Lock wrote:
> > On Sun, Feb 21, 2010 at 05:17:37PM -0800, Tim Kientzle wrote:
> >>
> >> Could you try the current version of read_open_filename from:
> >>
> >> http://libarchive.googlecode.com/svn/trunk/libarchive/archive_read_
Hi!
Before this gets buried on -hackers in another thead... :)
I now have disks appear as block devices for Linux processes (there
already was commented out code for that in linux_stats.c, I hope my
version is now `correct enough' to be usable [1]), and I made a simple
patch to make lseek SEEK_
>> With gsoc just around the corner I think the project ideas page should
>> be updated and moving the whole thing to wiki or maintaining a similar
>> page on wiki(along with the original page) sounds good to me.
>>
> I'll take the bait and make the page on the wiki. However someone else
> will ha
Shrivatsan wrote:
Hi,
I am trying to understand how msleep() routine suspends the currently
executing thread. I see that msleep() calls sleepq_wait().
What I don't understand here is the way in which sched_lock mutex is
handled.
I took the following snippet from FreeBSD 6:
sleepq_wait(voi
On Tuesday 23 February 2010 2:34:11 am Shrivatsan wrote:
> Hi,
>
> I am trying to understand how msleep() routine suspends the currently
> executing thread. I see that msleep() calls sleepq_wait().
>
> What I don't understand here is the way in which sched_lock mutex is
> handled.
>
> I took t
Hi,
I make small patch for no build hastd without openssl.
Index: sbin/Makefile
===
--- sbin/Makefile (revision 204220)
+++ sbin/Makefile (working copy)
@@ -37,7 +37,7 @@ SUBDIR= adjkerntz \
growfs \
6 matches
Mail list logo