to me...man pages are -reference- material. They are not intended to be the
'right way' to learn something, but instead as a quick reference guide.
manual pages are intended to PROPERLY describe how program/function etc.
operates.
Of course, I doubt anyone can make a case for the 'one true right way' to
learn FreeBSD.
True.
I would never teach someone to read the man pages as a way to
familiarize themselves with...say...geom(8). (In fact, I'd love to find some
why?
The notion of a 'new user' is unfortunately too wide of a category to target
documentation to.
The problem of today is "persistent new user". "New user since first time
touched computer".
A secretary who's never seen anything but windows, a 5 year
old child, and a fresh PhD in computer science might all fit this category.
Each of these people requires different levels of teaching.
Secretary should not be FreeBSD admin, while of course can be FreeBSD
user.
Unix makes clear distinction between user and admin.
Modern computing style blurs it.
Everytime I see these discussions my mind flashes to a web based wiki where
everyone writes helpful information (like the Emacs Wiki) on various topics
and it's fairly well indexed so you can see related ideas. Does something
like this exist for FreeBSD?
No idea. What i HATE in very modern software is wiki-style
"documentation".
4) Adding features that are not really finished and in working state.
gjournal is an example, background fsck is another (everyone actually
ends in background_fsck=NO)
Well you have me there, I thought background fsck worked...I just left it on
because it's set like that in /etc/defaults/rc.conf.
snapshots do crash on big filesystems. And after background fsck often you
will find more errors by foreground fsck.
Anyway it is not a problem really.
Just don't make bulky virtual volumes of 100 disks, as it is not just slow
to fsck but dangerous.
if your server works for people that cannot stand half an hour of downtime
then change to 0 all /etc/fstab positions except of most important, then
after a crash do fsck after worktime.
with softupdates it is generally safe to run filesystem without fsck for
some time.
Of course in the same time where are hundreds of good things done, and
we all know it. But if people won't understand a problem NOW and fight
it, it will become worse.
If everyone is busy fighting evil, who is left to create the good? :)
First "good" must be needed. Now "good" is defined by democratic means buy
herd of "persistent newbies". Doing nothing is actually better than create
new "goods" like that.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
