Hello!
Downward from the heights where the tower is installed in which the Hurd
administration resides ;-) I'm asking the question: what is the state of
this year's GSoC project, libchannel? Fredrik, how are you coming along?
Regards,
Thomas
PS: Somewhen this weekend I should be able to work
At Tue, 12 Jun 2007 16:55:52 +0200,
Michael Banck wrote:
>
> On Tue, Jun 12, 2007 at 10:51:48AM -0400, Michael Casadevall wrote:
> > That makes sense, but why don't we still include a random module in
> > the source itself so people who are working on one at least can work
> > >from a common s
At Wed, 13 Jun 2007 10:31:33 +0200,
"christian nastasi" <[EMAIL PROTECTED]> wrote:
>
> [1 ]
> [1.1 ]
> Hi all,
> I'm working on the vfatfs translator and I'm trying to understand how it
> should be merged with the fatfs one.
> First of all I'm looking at the dir entries searching (diskfs_lookup_
Hello!
| btw, I've realized they is a bunch of warnings while compiling
| the Hurd, these should probably deserve killed
| somebody should try with gcc-4.2/gcc-4.3 :)
Here is the list when compiling with GCC 4.1. So far, I didn't try with
4.2 or 4.3.
This was with plain Hurd cvs HEAD,
Hello!
For the following list of warnings (which were also already included in
my previous email's list) I think (I didn't really check so far ;-) that
the following patch might eliminate a chunk of those. Alternatively we
would have to apply some `union'ing magic in a lot of places. From the
qu
Thomas Schwinge <[EMAIL PROTECTED]> writes:
> Hello!
Hi!
> Downward from the heights where the tower is installed in which the Hurd
> administration resides ;-) I'm asking the question: what is the state of
> this year's GSoC project, libchannel? Fredrik, how are you coming along?
Well to be h
Hi,
Thomas Schwinge, le Thu 14 Jun 2007 16:42:10 +0200, a écrit :
> From the quick glance I had, the problem is that MIG only handles data
> structures via the `vm_address_t' type, whereas in the C code those
> are pointers to structures.
But if I understand correctly, the problem is that doing t
Answering to myself.
Samuel Thibault, le Thu 14 Jun 2007 16:57:29 +0200, a écrit :
> Thomas Schwinge, le Thu 14 Jun 2007 16:42:10 +0200, a écrit :
> > From the quick glance I had, the problem is that MIG only handles data
> > structures via the `vm_address_t' type, whereas in the C code those
> >
Hello!
#v+
../../libdiskfs/boot-start.c: In function ???diskfs_start_bootstrap???:
../../libdiskfs/boot-start.c:223: warning: passing argument 2 of
???dir_lookup??? discards qualifiers from pointer target type
#v-
#v+
101const char *initname;
[...]
222err = dir_lookup (root_pt, ini
Follow-up Comment #1, task #5130 (project hurd):
I figure this is a good place to post. For anyone following IRC, I've been
fighting to get a working entropy device in the kernel, and finally managed
to get some entropy going (not much, but its only reading one source as of
writing, I'll fix that
10 matches
Mail list logo
