From: C H Forsyth <forsyth@vitanuova.com>
To: lucio@proxima.alt.za, 9fans@9fans.net
Subject: Re: [9fans] ape pwd.h not in sync ?
Date: Thu, 18 Dec 2008 19:12:52 +0000 [thread overview]
Message-ID: <80906635c8a816936247e8322daef4aa@vitanuova.com> (raw)
In-Reply-To: <228339633bc8110d58678382179f6644@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
in this case, i can't seen any point in providing pw_passwd
since no program that uses it (for anything non-trivial) could
work on Plan 9. in fact, it's not even useful on unix systems:
When shadow(5) passwords are enabled (which is default on many
GNU/Linux installations) the content of pw_passwd is usually not very
useful. [because the contents are hidden in another file]
so: the program that refers to it won't be ported to plan 9,
and probably won't work on unix. best just to fix it by removing the reference.
[-- Attachment #2: Type: message/rfc822, Size: 2273 bytes --]
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] ape pwd.h not in sync ?
Date: Thu, 18 Dec 2008 17:21:04 +0200
Message-ID: <228339633bc8110d58678382179f6644@proxima.alt.za>
> it won't work, so it's better to find that out when
> you compile the program rather than waste time compiling
> it only to fail when run.
It's an interesting philosophy, but it just bites you in a different
spot :-)
That said, it's obvious from the way the question was posed that there
is no single answer.
++L
prev parent reply other threads:[~2008-12-18 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 16:55 prem
2008-12-18 14:45 ` Charles Forsyth
2008-12-18 15:21 ` lucio
2008-12-18 19:12 ` C H Forsyth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80906635c8a816936247e8322daef4aa@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).