summaryrefslogtreecommitdiff
path: root/hurd
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2011-07-27 03:33:51 +0200
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2011-07-27 03:33:51 +0200
commit0488c48e764897b536769886814bbf3b3d279504 (patch)
tree63ee5a14052a615bfda74e2bc81a889deb1351a9 /hurd
parent32f77fe6a6acaf29dc2c494e9aa24c33ad3dd68a (diff)
parentb687f782572b127e8ae32f0df40250fb19ccd22b (diff)
Merge branch 'master' of flubber:~hurd-web/hurd-web
Diffstat (limited to 'hurd')
-rw-r--r--hurd/documentation/translator_primer.mdwn6
-rw-r--r--hurd/faq/off.mdwn4
-rw-r--r--hurd/translator/procfs/jkoenig/discussion.mdwn18
3 files changed, 27 insertions, 1 deletions
diff --git a/hurd/documentation/translator_primer.mdwn b/hurd/documentation/translator_primer.mdwn
index 4586a8e6..e5c8c160 100644
--- a/hurd/documentation/translator_primer.mdwn
+++ b/hurd/documentation/translator_primer.mdwn
@@ -41,7 +41,11 @@ Then you setup the translator /hurd/hello in the file/node hello.
After that you check the contents of the file, and the translator returns "Hello World!".
-To finish it, you tell the translator to go away from the file "hello" via "settrans -g hello" and verify that now the file is empty again.
+To finish it,
+you remove the translator from the file "hello"
+(and tell any active running instances to go away)
+via "settrans -g hello".
+Having done that, verify that now the file is empty again.
### Transparent FTP
diff --git a/hurd/faq/off.mdwn b/hurd/faq/off.mdwn
index 363436b0..64009101 100644
--- a/hurd/faq/off.mdwn
+++ b/hurd/faq/off.mdwn
@@ -19,3 +19,7 @@ will not work. Simply use the equivalent shortcut
$ halt
which is provided natively on GNU/Hurd, instead of from SYSV runlevels.
+
+Note that due to a bug,
+we [[recommend you run syncfs|open_issues/sync_but_still_unclean_filesystem]]
+prior to issuing the `halt` command.
diff --git a/hurd/translator/procfs/jkoenig/discussion.mdwn b/hurd/translator/procfs/jkoenig/discussion.mdwn
index b66af7de..64e3776e 100644
--- a/hurd/translator/procfs/jkoenig/discussion.mdwn
+++ b/hurd/translator/procfs/jkoenig/discussion.mdwn
@@ -166,3 +166,21 @@ IRC, freenode, #hurd, 2011-03-28
mentoring the previous procfs implementation
<antrik> (though I never got around to look at his buggy code...)
<jkoenig> ok
+
+IRC, freenode, #hurd, 2011-07-22
+
+ <pinotree> hm, why /proc/$pid/stat is 600 instead of 644 of linux?
+ <jkoenig> pinotree, it reveals information which, while not that sensitive,
+ would not be available to users through the normal proc interface.
+ <jkoenig> (it's available through the ps command which is setuid root)
+ <jkoenig> we discussed at some point making it 644, IIRC.
+ <pinotree> hm, then why is it not a problem on eg linux?
+ <jkoenig> (btw you can change it with the -s option.)
+ <jkoenig> pinotree, it's not a problem because the information is not that
+ sensitive, but when rewriting procfs I preferred to play it self and
+ consider it's not procfs' job to decide what is sensitive or not.
+ <jkoenig> IIRC it's not sensitive but you need the task port to query it.
+ <jkoenig> like, thread times or something.
+ <pinotree> status is 644 though
+ <jkoenig> but status contains information which anyone can ask to the proc
+ server anyway, I think.