Thanks. I put that fix in. If all is now well, please close the PR.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Hello,
there was a discussion about Shadowfs' write support on IRC (#hurd @
openprojects.net) and Marcus suggested to post the conclusions - so
here they are.
The first question was: If shadowfs supports having an explicitely
specified writable filesystem[0], shadowfs might has to create whole
d
Moritz Schulte <[EMAIL PROTECTED]> writes:
> ext2fs.static: ../../libdiskfs/dir-renamed.c:140: diskfs_rename_dir:
> Assertion `tmpnp == fdp' failed.
Fix:
--- dir-renamed.c.orig Fri Oct 12 05:35:48 2001
+++ dir-renamed.c Fri Oct 12 04:40:32 2001
@@ -137,12 +137,12 @@ diskfs_rename_dir (st
Package: hurd
Version: N/A
Severity: normal
Hi,
the Assertion failure:
ext2fs.static: ../../libdiskfs/dir-renamed.c:140: diskfs_rename_dir:
Assertion `tmpnp == fdp' failed.
here it's reproducible with the following commands:
mkdir foobar
chmod 0 foobar
mv foobar /somewhere # CRASH.
m
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
> Where should code for a Hurd on L4 project be placed? Would these types
> of changes be something for bug-hurd?
There is a mailing list <[EMAIL PROTECTED]>.
Its members can tell you what they think.
I am always interested in seeing anybody's Hurd changes, and I will see
them if you post to bug
Where should code for a Hurd on L4 project be placed? Would these types
of changes be something for bug-hurd?
-- Ian
~~
Ian Duggan[EMAIL PROTECTED]
http://www.ianduggan.net
___
On Sat, Aug 11, 2001 at 04:50:18PM -0400, Roland McGrath wrote:
> Then run make check on this libc build and compare those results to what
> you got from make check on your non-libio build of libc. We might as well
> fix everything we can find with libc's own test programs before worrying
> abou
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
14 matches
Mail list logo
