Which Directory Service do you use for your network?
None NIS LDAP LDAP + Kerberos Samba Active Directory eDirectory other ( 793 votes ~ 15 comments )
You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.
To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.
This is the comment you were replying to, attached to the article Logical Volume Management: How PVs form VGs for LVs:
#2 Re: Logical Volume Management: How PVs form VGs for LVs Posted by Utumno (61.229.xx.xx) on Tue 22 Apr 2008 at 17:38 A general comment conc. the first paragraph: pretty much everything in OSS suffers from what I call 'feature oriented' documentation. Try searching online for info on , say, SELinux, or mutt, LVM or anything else. You'll find a lot of articles explaining all the little features, you'll find man pages of obscure commands, but you rarely will find THE BIG PICTURE. All the documentation is 'feature oriented' i.e. is a long manual describing all the low-level features of the system in question. I - and I suspect I am not alone here - very much prefer 'task oriented' manuals: concise info about how to do a particular thing with the system and WHY would I want to do it this way ( advantages over old system this one is replacing ). Here's a reason why 'task oriented' is better. Study case: LVM. Say a user is installing Debian for the first time and the partitioner offers him a choice: old-school partitioning or LVM. The user knows how he would like the system to preform, but he doesn't know if LVM or traditional partitions are better for his needs. He knows the ends, but doesn't know the means. So he does a search online on LVM and what does he find? A lot of low-level info how to resize, mirror, backup and whatnot. But that is all worthless! What he would like to find is a concise document explaining the differences between partitioning and LVM, and a 'task oriented' manual so he can see what is possible with LVM. That will get him started. When he is into it already and wants to do something more advanced which is not covered by the concise 'task oriented' manual, he probably already feels the system well enough to figure out the details himself. With the 'feature oriented' manuals one often has to read the whole damn 300 page manual to figure out if the system in question is even able to do what one needs!
A general comment conc. the first paragraph: pretty much everything in OSS suffers from what I call 'feature oriented' documentation.
Try searching online for info on , say, SELinux, or mutt, LVM or anything else. You'll find a lot of articles explaining all the little features, you'll find man pages of obscure commands, but you rarely will find THE BIG PICTURE. All the documentation is 'feature oriented' i.e. is a long manual describing all the low-level features of the system in question. I - and I suspect I am not alone here - very much prefer 'task oriented' manuals: concise info about how to do a particular thing with the system and WHY would I want to do it this way ( advantages over old system this one is replacing ).
Here's a reason why 'task oriented' is better. Study case: LVM.
Say a user is installing Debian for the first time and the partitioner offers him a choice: old-school partitioning or LVM. The user knows how he would like the system to preform, but he doesn't know if LVM or traditional partitions are better for his needs. He knows the ends, but doesn't know the means.
So he does a search online on LVM and what does he find? A lot of low-level info how to resize, mirror, backup and whatnot. But that is all worthless! What he would like to find is a concise document explaining the differences between partitioning and LVM, and a 'task oriented' manual so he can see what is possible with LVM.
That will get him started. When he is into it already and wants to do something more advanced which is not covered by the concise 'task oriented' manual, he probably already feels the system well enough to figure out the details himself.
With the 'feature oriented' manuals one often has to read the whole damn 300 page manual to figure out if the system in question is even able to do what one needs!
Posting Format:
Inappropriate comments will be removed.
Some help on entry formatting is available
Username:
Password:
[ Advanced Login ]
Register Account
