I prefer this ...
--- rc.conf.8 Tue Feb 11 21:24:16 2014
+++ rc.conf.new.8 Fri Jan 3 00:44:18 2014
@@ -47,11 +47,11 @@
.Pp
It is advisable to leave
.Nm rc.conf
-untouched, and instead create and edit a new
+untouched. The
+.Nm rc.conf
+file includes a check for
.Nm rc.conf.local
-file
"Strongly suggest" is too eager for my taste.
Besides, as far as brains gaps go this is clearly not the problem here.
"It is advisable" seems the BSD way.
My taste runs to this ...
--- rc.conf.8 Tue Feb 11 21:24:16 2014
+++ rc.conf.new.8 Thu Jan 2 23:29:58 2014
@@ -47,11 +47,14 @@
.Pp
Rod Whitworth
> I feel that date should spit out an error message rather than
> crash even if it only happens when some idiot plays with the numbers.
Every time you do that I get a little bit sadder.
Leave something for me.
Having read su and then group it struck me that this is disingenuous,
for want of a much better word:
A user is automatically in a group if that group was
specified in their passwd(5) entry and does not need to be added to that
group in the group file.
If this is intended on the part of
Hey.
I noticed adding a user to wheel doesn't provide su capability
automatically. This is described in su(1).
I though it might be useful to mention it in group(5) also.
--- group.5 Sun Dec 9 14:14:58 2012
+++ group_change.5 Sun Dec 9 15:07:29 2012
@@ -81,7 +81,13 @@
.Xr passwd 5
en
At the sake of running out of internet here's a little clarification ...
... this ...
-> input channela
channela output ->
-> input channelb
channelb output ->
-> input channelc
channelc output ->
-> input channeld
channeld output ->
-> input groupA (a&b)
groupA (a&b) output ->
-> input groupB (c
Hi.
Sviatoslav Chagaev <0x1392 () gmail ! com>
> I have absolutely no idea. I'm not an audio equipment manufacturer.
I have used many consoles ... digital and analogue ones ... "live" and
in studios.
I also have an electronics background - digital and analogue ... and
repaired many consoles.
I've