At Tue, 7 Aug 2012 23:55:12 +0200,
Thomas Schwinge wrote:
> > It's generic code. At least glibc keeps generic code around, if I
> > recall correctly. Further, one of the very nice things about this
> > libpthread is that it is really easy to integrate into a new OS (or
> > even use in a kernel).
Hi!
On Sat, 04 Aug 2012 16:17:29 +0200, "Neal H. Walfield"
wrote:
> At Sat, 4 Aug 2012 15:56:01 +0200,
> Thomas Schwinge wrote:
> > On Sat, 04 Aug 2012 15:16:22 +0200, "Neal H. Walfield"
> > wrote:
> > > At Sat, 4 Aug 2012 15:02:46 +0200,
> > > Thomas Schwinge wrote:
> > > > > > * signal/READM
At Sat, 4 Aug 2012 15:56:01 +0200,
Thomas Schwinge wrote:
> On Sat, 04 Aug 2012 15:16:22 +0200, "Neal H. Walfield"
> wrote:
> > At Sat, 4 Aug 2012 15:02:46 +0200,
> > Thomas Schwinge wrote:
> > > > > * signal/README: Likewise.
> > > > > * signal/TODO: Likewise.
> > > > > * signal/kill.c: Likewise
Hi!
On Sat, 04 Aug 2012 15:16:22 +0200, "Neal H. Walfield"
wrote:
> At Sat, 4 Aug 2012 15:02:46 +0200,
> Thomas Schwinge wrote:
> > > > * signal/README: Likewise.
> > > > * signal/TODO: Likewise.
> > > > * signal/kill.c: Likewise.
> > > > * signal/pt-kill-siginfo-np.c: Likewise.
> > > > * signal
At Sat, 4 Aug 2012 15:02:46 +0200,
Thomas Schwinge wrote:
> > > master-viengoos and its successor, master-viengoos-on-bare-metal.
> >
> > master-viengoos is an implementation of Viengoos that runs on L4.
> > viengoos-on-bare-metal runs directly on x86-64 (and it a bit more
> > advanced) and provid
Hi!
On Sat, 04 Aug 2012 13:02:10 +0200, "Neal H. Walfield"
wrote:
> At Sat, 4 Aug 2012 12:34:28 +0200,
> Thomas Schwinge wrote:
> > There has been a libpthread port for Hurd on L4 use, which is dead, and
> > has been superseded by a Viengoos port, which has its own branches:
>
> For what it is
I think these are also used by the Viengoos port. Are you suggesting
to remove both the L4 and the Viengoos ports or just the L4 port?
> Also, I propose to remove the incomplete and unmaintained PowerPC port.
> OK?
I have no objections to this.
> In August 2008, Neal has been porting ove
nd unmaintained PowerPC port.
OK?
Remove PowerPC port.
* TODO: Update.
* sysdeps/powerpc/bits/machine-lock.h: Remove file.
* sysdeps/powerpc/bits/memory.h: Likewise.
* sysdeps/powerpc/bits/spin-lock.h: Likewise.
* sysdeps/powerpc/machine-sp.h: Likewise.
* sysdeps/powerpc/pt-machdep.h: Likewise
Hi,
José Salaver Torres <[EMAIL PROTECTED]> wrote:
> I have been searching for a project about making a port for powerpc of
> the gnu-Mach microkernel, the only thing I have found is a project for
> making run the osf-mach into Hurd, that seems crap, because I have read
> that osf-mach doesn't ha
José Salaver Torres wrote:
I have been searching for a project about making a port for powerpc of
the gnu-Mach microkernel, the only thing I have found is a project for
making run the osf-mach into Hurd, that seems crap, because I have read
that osf-mach doesn't have a GPL license.
I have knowledg
José Salaver Torres <[EMAIL PROTECTED]> writes:
> I have been searching for a project about making a port for powerpc of
> the gnu-Mach microkernel, the only thing I have found is a project for
> making run the osf-mach into Hurd, that seems crap, because I have read
> that osf-mach doesn't have a
I have been searching for a project about making a port for powerpc of
the gnu-Mach microkernel, the only thing I have found is a project for
making run the osf-mach into Hurd, that seems crap, because I have read
that osf-mach doesn't have a GPL license.
I have knowledge of C and POSIX, so what c
I have been searching for a project about making a port for powerpc of
the gnu-Mach microkernel, the only thing I have found is a project for
making run the osf-mach into Hurd, that seems crap, because I have read
that osf-mach doesn't have a GPL license.
I have knowledge of C and POSIX, so what c
I started integrating some of your osfmach-related changes a while ago,
doing it piecemeal and cleaning things up along the way. I'm so far
avoiding the OSFMACH #ifdef and using specific feature checks instead.
Where did you get your osfmach and its development headers from? I got
osfmk from cv
Hi,
I've finally found the time to update my Hurd and create a patch for it to
run on OSF Mach. See http://huizen.dds.nl/~pjbruin/hurd/hurd.patch.
It still has many bugs, but it does work in some way (at least on my
machine :-) ).
Peter Bruin
[EMAIL PROTECTED]
Roland McGrath <[EMAIL PROTECTED]> writes:
> Of course, I also want to thank you again for working
> on the port. It's very exciting!
Ditto!
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Great! I have already integrated the "glibc-hurd-powerpc.patch" part of
the changes into libc. I am doing some rearranging of the libc code while
integrating your changes, to reduce copied code and so forth, and various
other nits. I am not yet able to try compiling for ppc, so I may have
intro
Hi,
I didn't know my mailer did that (I have to use Mac OS for e-mail, because
my modem isn't supported by Linux). I have put my files on the web,
http://huizen.dds.nl/~pjbruin/hurd/
Peter
>On Sat, Oct 27, 2001 at 09:09:15PM +0200, Peter Bruin wrote:
>> Hi,
>>
>> I'm sorry I didn't post my chan
>> I'm sorry I didn't post my changes earlier, but I was trying to get glibc
>> 2.2.4 to work and make patches for that. Here are my changes for glibc;
>> I'll post my changes to the Hurd as soon as possible,
>
> can you repost them in a sane format, like ASCII or uuencoded?
> The Debian macutils
On Sat, Oct 27, 2001 at 09:09:15PM +0200, Peter Bruin wrote:
> Hi,
>
> I'm sorry I didn't post my changes earlier, but I was trying to get glibc
> 2.2.4 to work and make patches for that. Here are my changes for glibc;
> I'll post my changes to the Hurd as soon as possible,
Hi,
can you repost t
From: Derek Fults <[EMAIL PROTECTED]>
Date: Fri, 12 Oct 2001 13:09:17 -0500
I am also working on trying to port Hurd to OSF mach. I need to
get a hold of a mig that generates the correct code for OSF mach,
(without typchecking). Peter Bruin said he could get me one in a
couple
10 October 2001 14:58, Roland McGrath wrote:
> > The PowerPC port of the Hurd that I'm working on is now partially
> > working; I've compiled bash, textutils and fileutils, most of which
> > runs. Ext2fs runs in read-only mode, but often crashes in writable
> > mod
I have also looked at the mips code, so it could also be based on that (I don't
have my code here, so I'm not sure). I haven't tried 'cat' yet, but C-c doesn't
work as far as I have tried, so rpc_trampoline is probably buggy.
You can get the powerpc manuals at www.mot-sps.com or www.chips.ibm.com
Mark Kettenis did some work a while back on using the hurd with osfmach on
x86. Probably that is mostly the same architecture-independent stuff
(differences in the IPC system between mach3 and osfmach) Peter has dealt
with for the ppc osfmach.
I have no clue about the status of the osfmach pa
> I stole much of the signal code from sysdeps/mach/hurd/alpha (is there an
> Alpha port of the Hurd?).
Yowza! No, there has never been a working Alpha port of the Hurd. There
once was an Alpha port of CMU Mach 3.0, so it was feasible enough, but it
never actually happened. I really don't rec
> I have ported the Hurd to OSF Mach (in fact, I haven't done anything with
> Mach, I just use the version that comes with MkLinux). You can indeed run
> the Hurd from within MkLinux, but it can't read from the console because
> Linux also has the console open; it might be possible to fix that.
--- Peter Bruin <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have ported the Hurd to OSF Mach (in fact, I haven't done
> anything with
> Mach, I just use the version that comes with MkLinux). You can
> indeed run
> the Hurd from within MkLinux, but it can't read from the console
> because Linux
> also h
I stole much of the signal code from sysdeps/mach/hurd/alpha (is there an Alpha
port of the Hurd?). Actually, there is at least one bug in my powerpc code: in
sigreturn, all the registers are restored except for the one (CTR) which holds
the return value right before returning. I don't know if the
Hi,
I have ported the Hurd to OSF Mach (in fact, I haven't done anything with
Mach, I just use the version that comes with MkLinux). You can indeed run
the Hurd from within MkLinux, but it can't read from the console because Linux
also has the console open; it might be possible to fix that. Maybe
Peter,
What you have done is jolly impressive, congratulations.
> "PB" == Peter Bruin <[EMAIL PROTECTED]> writes:
PB> Most changes I had to make were either processor-related or
PB> had to do with the differences between GNUMach and OSF Mach
PB> (which already
> Most changes I had to make were either processor-related or had to do
> with the differences between GNUMach and OSF Mach (which already existed
> on the PowerPC, so that I didn't have to worry about getting Mach to
> work). And _I_ was amazed that I didn't have to change anything in the
> Hurd
Quoting Roland McGrath <[EMAIL PROTECTED]>:
> > The PowerPC port of the Hurd that I'm working on is now partially
> > working; I've compiled bash, textutils and fileutils, most of which
> > runs. Ext2fs runs in read-only mode, but often crashes in writable
>
> The PowerPC port of the Hurd that I'm working on is now partially
> working; I've compiled bash, textutils and fileutils, most of which
> runs. Ext2fs runs in read-only mode, but often crashes in writable
> mode. Exec crashes when trying to run shell scripts. There are man
Hi,
The PowerPC port of the Hurd that I'm working on is now partially working; I've
compiled bash, textutils and fileutils, most of which runs. Ext2fs runs in
read-only mode, but often crashes in writable mode. Exec crashes when trying to
run shell scripts. There are many other bu
34 matches
Mail list logo
