Michael Banck wrote:
I get this error on two different machines, a P2-400 and a P-M-1500.
Marco told me that this error is also experienced by several other
people.
Yes, I've often experienced this on some machines too. There were some
clues in the mailing lists, but I couldn't find them with Goo
I think this is a good idea. We need updates for detailed information, and cosmetic.
People will benefit a lot more from a "well" written manual of great detail and easy
usage.
hde
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/
Why do you not do the Hurd Reference Manual in something like a
Wiki,
Because of the following:
* You can't read it offline
* You can't make it into a book (the FSF makes money by selling books,
a good thing)
* You can't print it (a subset of the above)
* You can't convert it to some r
Why do you not do the Hurd Reference Manual in something like a Wiki, it's faster,
It's easy to remodel, it's more simple to update, it's exciting to who will edit. To
do official versions you can put a person to read the updates and rewrite.
--
__
Che
[sorry for the long delay]
Here is Jeroen's patch that makes glibc's bug-fseek test case pass.
POSIX says that one should fail with EINVAL when the file posistion is
smaller than 0.
libdiskfs/ChangeLog
2004-05-08 Jeroen Dekkers <[EMAIL PROTECTED]>
* libdiskfs/io-seek.c (diskfs_S_io_se
The top priority is to have accurate details in some usable form. They can
always be rearranged later according to one's idea of best presentation
style. So as far as I am concerned, people who are going to put time into
actually keeping the technical details up to date and making them complete
c
GNU manuals have always been intended to serve as both good
introductions that can be read straight through, and as reference
manuals. You don't have to give a manual a meaningless structure
to make it easy to find things by name. Good indexes and good
menus can do that.
Well, the
GNU manuals have always been intended to serve as both good introductions
that can be read straight through, and as reference manuals. You don't
have to give a manual a meaningless structure to make it easy to find
things by name. Good indexes and good menus can do that.
___
Allways during my late night hacking sessions I try to find something
useful todo while waiting for compile jobs, this is tonights task.
Doing a overhaul of the Hurd Reference manual.
The major grief I have with it is that it is organised in a stupid
way. The following "list" is how I want to reo
Hi Michael!
It was ages since I did any work with OSKit-Mach, glad to see
that someone is still trying. Ognyan and I once fiddled around
with these pages on the wiki, now and again I see Ognyan poking
with them:
http://hurd.gnufans.org/bin/view/Mach/BuildingOskitMach
http://hurd.
Hello,
I tried to build and run oskit-mach today. Building (see below) went
fine, but when I try to boot it, I get the following (transcribed):
Welcome to GNU Mach 1.91!
Kernel page fault at address 0x1, eip = 0x1
Kernel Page fault trap, eip 0x1
kernel trap, type 14, code = 0
Dump of trap_state a
Title: lois stein_onsrud
E-mail Рассылка
Предлагаем провести массовую электронную
рассылку вашей информации по адресам электронной почты
юридических лиц и частных лиц Москвы и России.
Это самая результативная и недорогая реклама Вашего бизнеса.
Оформление макета -
I am setting up a sub-hurd to get some testing done. I used hurd
from cvs. Which lead me to a question. There is no way for you to
specify an alternate root dir for installing the hurd translators
is there? See, when you compile and install hurd, hurd always puts
all of the transl
13 matches
Mail list logo
