Hi,
Currently, setsid(0) always return 1, while it should return the sid of
the calling process. Here is a proposed patch:
[hurd]/proc/Changelog
2006-01-17 Samuel Thibault <[EMAIL PROTECTED]>
Fix setsid(0).
* pgrp.c (S_proc_getsid): When pid == 0, use `callerp' argument
Hi!
On Mon, Jan 16, 2006 at 11:52:43AM -0200, Matheus Morais wrote:
> There exist support to run wireless cards in Hurd?
No, not yet.
> If no, its possible (with
> the currently workable system) design that kind of device driver to Hurd?
> Its already exists a lot of workable drivers in GNU/Linu
On Mon, Jan 16, 2006 at 11:52:43AM -0200, Matheus Morais wrote:
> There exist support to run wireless cards in Hurd? If no, its possible (with
> the currently workable system) design that kind of device driver to Hurd?
> Its already exists a lot of workable drivers in GNU/Linux and FreeBSD, its
> p
Matheus Morais <[EMAIL PROTECTED]> writes:
>There exist support to run wireless cards in Hurd? If no, its possible
>(with the currently workable system) design that kind of device driver
>to Hurd? Its already exists a lot of workable drivers in GNU/Linux and
>FreeBSD, its possible
Hi,
On 1/16/06, Matheus Morais <[EMAIL PROTECTED]> wrote:
> There exist support to run wireless cards in Hurd? If no, its possible (with
> the currently workable system) design that kind of device driver to Hurd?
> Its already exists a lot of workable drivers in GNU/Linux and FreeBSD, its
> possib
"Alfred M\. Szmidt" <[EMAIL PROTECTED]> writes:
> I don't recall giving you any kind of permission to post private
> messages to a public list. This is what is inapprorpiate behaviour.
In this context, it is entirely appropriate.
Alfred, you don't get to declare the list standards. It is clear
There exist support to run wireless cards in Hurd? If no, its possible
(with the currently workable system) design that kind of device driver
to Hurd? Its already exists a lot of workable drivers in GNU/Linux and
FreeBSD, its possible port them to work on Hurd?
Thanks
Matheus Morais
_
