Seeing all that repeated change makes me think we should have an
iohelp function to do the computation and checking for you, e.g.
error_t iohelp_seek (off_t *stored_pos, off_t end_pos,
off_t offs, int whence, off_t *new_offs);
Would you like to do that?
Thanks,
Roland
___
Marco Gerards <[EMAIL PROTECTED]> writes:
> Added to that, if anyone has a patch, just send it in. I am willing
> to proof read every patch that makes sense. And I am sure a lot of
> people will do the same.
I would be happy to. I am possibly going to have a small patch for the ref
manual here
no one is interested in working on the Hurd Reference Guide.
I am.
I can not remember a single patch for it sent to the mailinglists
as long as I am subscribed (almost 3 years).
Then you have utterly crappy memory. James has sent patches for it on
occassions during these 3 years you n
Yaakov Nemoy <[EMAIL PROTECTED]> writes:
>> It can be better than one Wiki, but I think that we need a on-line
>> version that the people can read the newest modifications. Because
>> If only a group, or one person, works in this job the manual could
>> turn boring and discourage people to send f
Package: hurd
Version: 20040508-4 UNRELEASED
Severity: important
Tags: sid patch
SVN hurd package doesn't really set SUID bit for /bin/login because
chmod u+s is not executed on the correct file. The attached patch sets
SUID of /bin/login and other SUID programs.
Regards,
ogi
Index: rules
=
Package: hurd
Version: 20040508-4 UNRELEASED
Tags: sid patch
The fsck is called with options -C -R -A. But -R option is for not
fsck:ing the root filesystem. The attached patch fixes this, and also
correctly remounts the root filesystem.
Regards,
ogi
--- rc 2004-09-26 19:58:38.0 +0300
Why oh why won't you two shutup and start writting documentation
instead? :-)
You _will_ have to send a patch here no matter what, you _will_ have
convert it from the wiki format to texinfo and back again-- waste of
time, IMHO. Why not skip those extra steps and just do it the way it
was meant to
> > > It can be better than one Wiki, but I think that we need a on-line version that
> > > the people can read the newest modifications. Because If only a group, or one
> > > person, works in this job the manual could turn boring and discourage people to
> > > send fixes. I think that we need m
> >
> > It can be better than one Wiki, but I think that we need a on-line version that
> > the people can read the newest modifications. Because If only a group, or one
> > person, works in this job the manual could turn boring and discourage people to
> > send fixes. I think that we need most
>
> It can be better than one Wiki, but I think that we need a on-line version that the
> people can read the newest modifications. Because If only a group, or one person,
> works in this job the manual could turn boring and discourage people to send fixes.
> I think that we need most people po
> "Leonardo Pereira" <[EMAIL PROTECTED]> writes:
>
> > I had said that frow Wiki one person can get the texts, confer they and write the
> > others kind of manual. This can be used only to create the new manual, because
> > it's faster, after you can get the new manual and update it how do you w
I had said that frow Wiki one person can get the texts, confer they and write the
others kind of manual. This can be used only to create the new manual, because it's
faster, after you can get the new manual and update it how do you want.
--
__
Check o
(B $BL$>5Bz9-9p"((J
$Bhttp://ochibashigure.mydns.jp/scripts/deleteform.html $B!!(J
$B!!(Jhttp://akatukinotume.minidns.net/scripts/deleteform.html
(B $BHNGd5~6h2r#1#0#0!]#1(J
(B $BEEOC(J0774-55-6699
(B
(B 8$B7n!A(J9$B7n$K=8$a$?(J100$BK|%a!<%k$r%5!<%S%9Cf!*(J
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
14 matches
Mail list logo
