Announcing the slow burial of the Hurd Wiki

[Joachim Nilsson]

Hi everybody!

This is a bit of a sad post.  It's the announcement of the slow burial of
the Hurd Wiki at http://hurd.gnufans.org

For those of you who have contributed during the years this may not
come as much of a surprise.  Activity has been low, the wiki engine
never got upgraded and account registration has turned into a slow
and tedious manual process ...

... don't get me wrong.  Everything works, the site has an ever so high
availability and already registered users can work just as expected.
But the site admin (I) have gone more and more absent due to work, life,
slowly expanding family and shifted interests.  So account activations
have almost stopped (I have 70 new not yet activated registrations in my
inbox since May) and sudden spurs of Wiki spam, which I've much cleaned
up myself through the years, have gone much unfixed.  Some brave souls
have taken it upon themselves to help out using the web interface to
revert pages spam, but that takes a lot of time.

Oh well, time to get to the point.  Despite its controversy among some in
the Hurd community I feel that a lot of the content in the wiki is still
useful.
It's organized in a fairly decent structure, has both well worded and poor
content.  All written in a fairly simple syntax that can be easily
converted to
just about anything popular these days: XML, MarkDown, reST, or any
other "WikiFormat" out there. (I've seen you guys talking about Ikiwiki
and others as a replacement.)

To aid any such venture I'm willing to take the time to create a tarball
of the whole TWiki setup, including webserver configuration and even
provide some limited support during moving/converting to another site/setup.

Until this time (if ever anyone steps up to the plate) the current setup
at gnufans will continue to run for as long as Mr. Deepak Goel is kind
enough to sponsor the domain name fee and as long as there is disk space
on the server.

To reduce the risk of my missing any direct questions or suggestions
about this message, please CC me to my reply-to address above.

Oh, sorry for the x-post.

Cheers
 /Jocke - Hurd Wiki admin



___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: Re : upgrade

[Thomas Schwinge]

Hello!

On Wed, Jul 12, 2006 at 06:41:43PM +0530, [EMAIL PROTECTED] wrote:
> I had just been a week at IIIT, Hyderabad - http://iiit.ac.in. The
> faculty there has agreed to pool in research students and scholars there
> to assist in the development of Hurd.

That's very interesting to hear.  :-)

But first we should clarify a few issues.  Are you aware that the current
Hurd's implementation (and design) are currently not as actively pushed
forward as they were is in the past?

A number of people instead began to reconsider issues in the Hurd's
design (see the l4-hurd mailing list's archives for example,
).  This includes both the
actual Hurd's design, as well as the underlying micro kernel.  A very
early, incomplete draft of this ``new Hurd'''s design is available at
 and the beginning of
documenting some issues at
.  Unfortunately its main
pioneers, Marcus Brinkmann and Neal Walfield (and a number of other
people, mostly on the l4-hurd mailing list), can't -- at the moment --
dedicate as much time to this project as it would need.  So, there is
currently no possibility to directly contribute to this effort, as far as
I can see.

If you instead think it is feasible to invest time into the current Hurd
on Mach implementation, there are tons of loose ends where work would be
possible.


> It has been over 20 years of development. I have undertaken to do a
> qualitative study of the development during this period.
> Q2) Where can I find the valid archives ?

You mean like mailing list archives?  They're accessible from
 and
.  Very old stuff, the archives of
the hurd-folks mailing list which is documenting parts of the Hurd's
genesis, are available at
.

There is no written history, as far as I know.  Only bits here and there.


Regards,
 Thomas


___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: upgrade

[Philip Charles]

On Sunday 16 July 2006 22:49, Thomas Schwinge wrote:
> Hello!
>
> On Wed, Jul 12, 2006 at 06:41:43PM +0530, [EMAIL PROTECTED] wrote:
> > I had just been a week at IIIT, Hyderabad - http://iiit.ac.in. The
> > faculty there has agreed to pool in research students and scholars
> > there to assist in the development of Hurd.
>
> That's very interesting to hear.  :-)
>
> But first we should clarify a few issues.  Are you aware that the
> current Hurd's implementation (and design) are currently not as
> actively pushed forward as they were is in the past?
>
> A number of people instead began to reconsider issues in the Hurd's
> design (see the l4-hurd mailing list's archives for example,
> ).  This includes both
> the actual Hurd's design, as well as the underlying micro kernel.  A
> very early, incomplete draft of this ``new Hurd'''s design is available
> at  and the beginning of
> documenting some issues at
> .  Unfortunately its
> main pioneers, Marcus Brinkmann and Neal Walfield (and a number of
> other people, mostly on the l4-hurd mailing list), can't -- at the
> moment -- dedicate as much time to this project as it would need.  So,
> there is currently no possibility to directly contribute to this
> effort, as far as I can see.
>
> If you instead think it is feasible to invest time into the current
> Hurd on Mach implementation, there are tons of loose ends where work
> would be possible.
>
> > It has been over 20 years of development. I have undertaken to do a
> > qualitative study of the development during this period.
> > Q2) Where can I find the valid archives ?
>
> You mean like mailing list archives?  They're accessible from
>  and
> .  Very old stuff, the archives
> of the hurd-folks mailing list which is documenting parts of the Hurd's
> genesis, are available at
> .
>
> There is no written history, as far as I know.  Only bits here and
> there.

Would the people at IIIT, Hyderabad be interested in taking over the 
production of the CD and DVD iso images?  I plan to retire from this task 
within the next six months.

Phil.

-- 
  Philip Charles; 39a Paterson Street, Abbotsford, Dunedin, New Zealand
   +64 3 488 2818Fax +64 3 488 2875Mobile 027 663 4453
 [EMAIL PROTECTED] - preferred.  [EMAIL PROTECTED]
  I sell GNU/Linux & GNU/Hurd CDs & DVDs.   See http://www.copyleft.co.nz


___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd

GNU Mach glue code update

[Richard Braun]

Hello,

As a first step to implementing the sound system, it looks almost
necessary to update the glue code. First, I'd like to know if anyone
has begun this work or intends to do it. Second, and if noone has
worked on this yet, what are the main steps and files to alter in
the gnumach-1-branch source tree to achieve this goal ?

-- 
Richard Braun


signature.asc
Description: Digital signature
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: GNU Mach glue code update

[Thomas Schwinge]

Hello!

On Sun, Jul 16, 2006 at 06:49:23PM +0200, Richard Braun wrote:
> As a first step to implementing the sound system, it looks almost
> necessary to update the glue code.

Yes, that'll be needed as soon as you want to integrate most device
drivers that are newer than Linux 2.0's.  A few newer ones provide
backwards compatibility, most notably the Donald Becker NIC drivers we're
using and the PCMCIA drivers Stefan Siegl has been working on, but that's
about it, as far as I know.


> First, I'd like to know if anyone has begun this work or intends to do
> it.

Not as far as I know.


> Second, and if noone has worked on this yet, what are the main steps
> and files to alter in the gnumach-1-branch source tree to achieve this
> goal ?

Basically the complete i386/linux/ and linux/ directories and some bits
like calling interrupt handlers, memory management, etc. which are
scattered over the GNU Mach sources.

Possibilities are a) updating the current glue code to a newer Linux
version, which will probably lead to rewriting most of it nevertheless or
b) just going ahead and write new glue code, be it again for Linux or --
for example -- some BSD, which I favor, mostly for unknown reasons.  ;-)

Using an approach (which was presented at last year's RMLL) like
 ``Unmodified Device
Driver Reuse and Improved System Dependability via Virtual Machines'' --
although being very interesting -- is most probably not feasible within
Mach's environment, I guess.


Regards,
 Thomas


___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd

[task #5497] nfs and nfsd

[Thomas Schwinge]

Update of task #5497 (project hurd):

  Status:None => In Progress
 Assigned to:None => mmenal 


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd

Re Re: upgrade

[doxa]

Dear Dr Jawahar,
Here's a request coming. If there are serious researchers there, this should be 
of great help to them.
Rgds,
CK Raju
Original Message ---
On Sunday 16 July 2006 22:49, Thomas Schwinge wrote:
> Hello!
>
> On Wed, Jul 12, 2006 at 06:41:43PM +0530, [EMAIL PROTECTED] wrote:
> > I had just been a week at IIIT, Hyderabad - http://iiit.ac.in. The
> > faculty there has agreed to pool in research students and scholars
> > there to assist in the development of Hurd.
>
> That's very interesting to hear.  :-)
>
> But first we should clarify a few issues.  Are you aware that the
> current Hurd's implementation (and design) are currently not as
> actively pushed forward as they were is in the past?
>
> A number of people instead began to reconsider issues in the Hurd's
> design (see the l4-hurd mailing list's archives for example,
> ).  This includes both
> the actual Hurd's design, as well as the underlying micro kernel.  A
> very early, incomplete draft of this ``new Hurd'''s design is available
> at  and the beginning of
> documenting some issues at
> .  Unfortunately its
> main pioneers, Marcus Brinkmann and Neal Walfield (and a number of
> other people, mostly on the l4-hurd mailing list), can't -- at the
> moment -- dedicate as much time to this project as it would need.  So,
> there is currently no possibility to directly contribute to this
> effort, as far as I can see.
>
> If you instead think it is feasible to invest time into the current
> Hurd on Mach implementation, there are tons of loose ends where work
> would be possible.
>
> > It has been over 20 years of development. I have undertaken to do a
> > qualitative study of the development during this period.
> > Q2) Where can I find the valid archives ?
>
> You mean like mailing list archives?  They're accessible from
>  and
> .  Very old stuff, the archives
> of the hurd-folks mailing list which is documenting parts of the Hurd's
> genesis, are available at
> .
>
> There is no written history, as far as I know.  Only bits here and
> there.

Would the people at IIIT, Hyderabad be interested in taking over the 
production of the CD and DVD iso images?  I plan to retire from this task 
within the next six months.

Phil.

-- 
  Philip Charles; 39a Paterson Street, Abbotsford, Dunedin, New Zealand
   +64 3 488 2818Fax +64 3 488 2875Mobile 027 663 4453
 [EMAIL PROTECTED] - preferred.  [EMAIL PROTECTED]
  I sell GNU/Linux & GNU/Hurd CDs & DVDs.   See http://www.copyleft.co.nz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd