Hello,
Starting today I will be working on a native Hurd debian-installer.
This is a Google Summer of Code project mentored by Samuel Thibault.
My original proposal is there[1], and I will be updating a roadmap[2]
page as I go. Of course I would welcome any kind of feedback about
them at any
[Jérémie Koenig]
I would also welcome suggestions about using the BTS to track my
progress. If I understand correctly, I could:
* track the bugs which I work on with a usertag
* pre-file wishlist bugs on the packages which I will need to change
* have a toplevel Hurd d-i bug which is
On Fri, 19 Apr 2002, Farid Hajji wrote:
As Wolfgang said, nothing will happen unless we get more volunteers
to help. There are some time constraints (like, we're waiting for
Pistachio etc...), but a lot of things can already be done right
now by people with some spare time ;-).
I'd like to
On Fri, Apr 19, 2002 at 11:19:00AM +0100, Dr. William Bland wrote:
I'd like to offer to help, but I'm not really sure how I can. Perhaps
it's still too early for people like me to do anything? I program in
C, Java and a little C++ but probably at more of an applications level
than what is
On Fri, Apr 19, 2002 at 09:55:46AM +0200, Farid Hajji wrote:
6. Driver Support: Two models are being investigated:
6.1: OSKit drivers
6.2: L4Env (http://os.inf.tu-dresden.de/L4/bib.html#l4env)
We're waiting for a release of L4Env.
Uh, that can take some time :)
It's not
It's not yet clear wether we should stick to Mach's device API
or if the oskit-mach people are considering a totally new approach.
Basically, the drivers must be implemented in user-space (L4 API
sends INTs to driver threads through IPC, much like in Mach).
The Mach device
to L4
2. Free the world
3. Fix the filesystem size limitation
But seriously: I think most of the stuff won't be done in any particular
order, but as soon as somebody decides to do it. That's why I think we
don't need a roadmap.
Obviously, most of the things being worked on right now (like
Hello again!
The last mail I sent rendered a completely different discussion
than I initially intended. But all the talk about user space
drivers and such actually made me start thinking.
Is there currently any roadmap for the Hurd available?
If I try to clearify, I mean a general overview
The boot-floppies currently and most likely for woody also uses
libfdisk, its a small (20K) partitioning program. (see
http://cvs.debian.org/boot-floppies/utilities/libfdisk/ )
Is this still the plan? Or is it libparted now?
pgp7qY2PNZfSl.pgp
Description: PGP signature
On Sat, Oct 21, 2000 at 02:22:45PM +1100, Glenn McGrath wrote:
Marcus Brinkmann wrote:
On Fri, Oct 20, 2000 at 12:34:22PM +1000, Anthony Towns wrote:
On Fri, Oct 20, 2000 at 04:04:04AM +0200, Marcus Brinkmann wrote:
Some minimal ones:
* boot-floppies, some way of
Marcus Brinkmann wrote:
On Fri, Oct 20, 2000 at 12:34:22PM +1000, Anthony Towns wrote:
On Fri, Oct 20, 2000 at 04:04:04AM +0200, Marcus Brinkmann wrote:
Some minimal ones:
* boot-floppies, some way of installing the system in an
automated, fairly standard way that
Hi,
Note: The subject does not imply that we make the decision to release with
woody or not now. This is meant as a list of conditions that must be
fulfilled before we even can consider this. Maybe it is a motivation for you
to help to reach those conditions.
I am forwarding and replying to the
Okay, I've lined out everything for the Hurd web pages. These are now under
CVS. Anyone with a login on www.gnu.org should be able to access them with:
% export CVSROOT=:pserver:username@www.gnu.org:/home/www/cvs
% cvs login
enter password
% cvs get -d hurd-html html/software/hurd
See cvs(1)
At 10:33 -0600 1999-01-09, Gordon Matzigkeit wrote:
1) Releasing an official Debian glibc package that works on the Hurd.
I've finally gotten the Hurd parts of the Debian glibc packaging
basically stabilized. I've sent patches to Joel Klecker, and once he
and I have a chance to coordinate, I
From: Matthias Pfisterer [EMAIL PROTECTED]
Subject: Re: Hurd documentation roadmap
Date: Fri, 01 Jan 1999 19:06:57 +0100
I found that in the current Hurd pages important and unimportant
information, outdated and actual are mixed somewhat randomly. So I felt
it was necessary to have
hello
in the new year. Let's hope 1999 will become the breakthrough in Hurd
development.
Some notes about the documentation:
Web pages
-
I found that in the current Hurd pages important and unimportant
information, outdated and actual are mixed somewhat randomly. So I felt
It would be good to have a repository for Hurd documentation and a
maintainer(s)
to coordinate changes. There are several items in this area: 1) web pages,
2)
FAQs, 3) HOWTOs, 4) reference manuals. I don't believe that there's
currently
one place to go to find all of these
17 matches
Mail list logo