Интернет реклама
Результат сразу
E-mail рассылка
Юридические и физические лица
Россия, Москва, страны СНГ
h.
Where can I find the detailed explanation of why this patch is
required and how it works to fix the problems ? At the moment I can't
even seem to find an error message from an FTBFS log.
Ian.
Svante Signell writes ("Re: [Fwd: [ISC-Bugs #25979] What happened to the dhcp
patch in ISC-Bugs #24697 (Debian Bug #616290)?]"):
> On Thu, 2011-12-15 at 14:15 +, Ian Jackson wrote:
> > Where can I find the detailed explanation of why this patch is
> > required an
here is entirely understandable.
> > A reference to a mailing list thread may helpful as background
> > reading, but I'm afraid it does not meet the standard I would expect
> > for a patch submission.
>
> Are there any rules for what to include in a patch? I've never seen one.
Many projects have their own documents, but the general principles are
the same across many free software projects.
Ian.
from Linux, without needing a second machine. Using
oskit-mach, we'd hopefully attain benefits from gdb over serial for
dubuggind as well.
http://www.plex86.org
--Ian
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
there Hurd specific changes to glibc, and how long
does it take them to make it back to the the Debian source version?
Is there a list of patches against glibc that need to be maintained for
the Hurd to work properly?
-- Ian
~~
Ian
Hi,
I'm working to try to get the Hurd running on the L4 microkernel. What
is required for a minimal Hurd system?
-- Ian
~~~~~~
Ian Duggan[EMAIL PROTECTED]
http://www.iandugga
estigating.
I'm unfamiliar with Doors. I found a few pages about an old "Doors on
Linux" implementation that was abandoned for "general lack of interest".
Where could I find more info on this?
-- Ian
~~
Ian
f ports for
IPC so closely? Doesn't that limit it to certain types of microkernel? Is there
a more general notion of IPC that we could use that would allow more flexibility
in the choice of the underlying microkernel?
It seems to me that libports marries the H
re they currently use gnumachs'.
I understand what would be required for (1) better, so initially it seems
attractive. However, as you pointed out, I don't see how useful that would be as
a resulting system. I think I will work on (2) and see where I can get to.
--
nOS to Solaris, and
weren't about to accept another switch. Google gave stuff when searching
for "spring os", "spring doors", and "linux doors".
A key thing to note, it looks like Doors is similar to Mach ports in
that it is handled in the kernel. We could of c
oesn't provide that, whatever does can clean the ports too.
This must be the way. I took a quick look over the L4 manuals to try to
find a way to be notified of task death, but I didn't see anything
obvious. There must be some sort of notification involved though, right?
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
> Be careful about one thing: if the same file occurs more than once in
> the archive, you must use the *last* occurrence, not the first, as the
> contents of the file. That might require scanning through the whole
> archive.
Scan the archive in reverse.
n the SERIAL Howto.
http://www.ibiblio.org/mdw/HOWTO/Serial-HOWTO.html
--Ian
--
~~
Ian Duggan[EMAIL PROTECTED]
http://www.ianduggan.net
ssued if the time between bytes being
received exceeds the timeout value. The hardware is a little smarter
than just issuing an interrupt at a regular interval.
-- Ian
~~~~~~
Ian Duggan
as long as "data ready"
is enabled. The Hurd code seems to be doing the same thing as the
corresponding Linux code.
It still sounds like flow control is kicking in somewhere along the line
and isn't being disabled when appropriate.
-- Ian
~~~~
ot of text
on the page. It would be nice if it could be organized into sections.
-- Ian
~~~~~~
Ian Duggan[EMAIL PROTECTED]
http://www.ianduggan.net
__
added to the project.
-- Ian
~~
Ian Duggan[EMAIL PROTECTED]
http://www.ianduggan.net
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http
this patch correctly for libgo.
Ian
On Tue, Jan 5, 2021 at 3:07 PM Samuel Thibault via Gcc-patches
wrote:
>
> Jeff Law, le mar. 05 janv. 2021 16:04:45 -0700, a ecrit:
> > Thanks. Installed.
>
> Thanks!
>
> Samuel
Unfortunately it's hard for me to judge. The most important skill
would be the ability to dig into some large code bases and understand
how to change them.
Ian
o port is implemented in a way that makes
> extensive use of switching stacks. So until this threadvar issue is
> resolved, there is probably no way to really proceed with the GCC Go port
> for GNU Hurd -- unless maybe this stack switching could be hacked around
> (Ian?), say, by limitin
On Thu, May 16, 2013 at 2:19 PM, Fotis Koutoulakis
wrote:
>
> Last but not least, I would like to know if you have some other proposition
> for me. Mr Ian could have a suggestion for the go part perhaps?
Make sure you can build and modify gccgo for some other target, e.g., GNU/Linux.
ted into glibc,
> our threadvar resolver could track back split-stack's initial_sp (where
> the threadvars live, I presume). But as split-stack is not generally
> implemented but currently only for x86 GNU/Linux, I suppose there's no
> real harm for GCC Go's usability when not hav
cgo is to use the process described at
https://golang.org/doc/gccgo_contribute.html. That explains how to
send changes to Gerrit in a way that is easy for me to review and
apply (Gerrit is itself free software). You are much more likely to
get a response if you are able to follow that approach.
Ian
be
talking about paravirt_ops/VMI and/or PV drivers at some point in
addition to vanilla int13 real mode devices (though the virtual BIOSes
will likely take care of this anyway).
- Ian C. Blenke <[EMAIL PROTECTED]>
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
GNU/Hurd.
>
Thanks. Committed as follows.
Ian
3ca4f43f50a3e8c7a398ea797220808b3318
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE
index c39aca9b1b0..59badf80f40 100644
--- a/gcc/go/gofrontend/MERGE
+++ b/gcc/go/gofrontend/MERGE
@@ -1,4 +1,4 @@
-092668d6ce6d7b3aff6797
27 matches
Mail list logo
