From: "Antonin Vecera" <antonin.vecera@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] error in fscons?
Date: Wed, 13 Jun 2007 10:20:01 +0200 [thread overview]
Message-ID: <10b109140706130120s77436246lf99d88d887a0ac64@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
Hi,
I got corrupted /adm/users while editing users on fscons after installation:
% con /srv/fscons
prompt: uname bootes bootes
prompt: uname adm +bootes
prompt: uname sys +bootes
prompt: uname sys -glenda
prompt: uname sys
sys:sys::?1k^&$#@ <- NONSENSE!!!
% cat /adm/users
adm:adm:adm:sys,bootes
bootes:bootes::
glenda:glenda:glenda:
none:none::
noworld:noworld::
sys:sys::adm <- NONSENSE!!!
upas:upas::
I think there is an error in fossil or fscons...
Antonin
[-- Attachment #2: Type: text/html, Size: 1053 bytes --]
next reply other threads:[~2007-06-13 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 8:20 Antonin Vecera [this message]
2007-06-13 13:18 ` Richard Miller
2007-06-14 8:37 ` Antonin Vecera
2007-06-14 8:06 ` Richard Miller
2007-06-14 10:26 ` Antonin Vecera
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=10b109140706130120s77436246lf99d88d887a0ac64@mail.gmail.com \
--to=antonin.vecera@gmail.com \
--cc=9fans@cse.psu.edu \
/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).