Richard Braun, le Thu 06 Nov 2014 16:39:48 +0100, a écrit :
> On Thu, Nov 06, 2014 at 04:33:26PM +0100, Samuel Thibault wrote:
> > In my memory, it's something like migrating threads which could make it
> > possible for more flexible ioctls.
>
> Not migrating threads, object mobility [1].
>
> [1]
On Thu, Nov 06, 2014 at 04:33:26PM +0100, Samuel Thibault wrote:
> In my memory, it's something like migrating threads which could make it
> possible for more flexible ioctls.
Not migrating threads, object mobility [1].
--
Richard Braun
[1] http://users.student.lth.se/cs07fh9/2009-hammar-hurd-m
Richard Braun, le Thu 06 Nov 2014 16:31:05 +0100, a écrit :
> On Thu, Nov 06, 2014 at 03:53:18PM +0100, Samuel Thibault wrote:
> > There used to be some investigation to redirect the ioctl function in
> > such case, but it wastn't integrated. I don't remember how it was
> > called, probably Richar
On Thu, Nov 06, 2014 at 03:53:18PM +0100, Samuel Thibault wrote:
> There used to be some investigation to redirect the ioctl function in
> such case, but it wastn't integrated. I don't remember how it was
> called, probably Richard remembers?
I don't remember anything being actually done for that
Svante Signell, le Thu 06 Nov 2014 13:09:49 +0100, a écrit :
> Can somebody verify this? The last entry in the structs below is a
> pointer and according to the link above the ioctl cannot be described
> with the _IOT macros.
Indeed.
> If it is not possible with ioctls, how to add Hurd support fo
Hi,
I am looking into the build failures of freeipmi (1.4.5-3) and found
that it seems impossible to define _IOT_req and _IOT_recv from the _IOT_
macros defined in /usr/include/i386-gnu/bits/ioctls.h and reading the
description on missing _IOT in
http://www.gnu.org/software/hurd/hurd/porting/guide
On Wed, Nov 05, 2014 at 12:35:26PM +0100, Riccardo Mottola wrote:
> Using the given debian CD, what's the best way to fix this problem,
> if possible? Without reinstalling once again, if possible.
> I could not access other consoles or saw meaningful errors on screen
> to report.
> thank you.
You'