On Thu, Dec 4, 2014 at 3:10 PM, Alessandro Selli <alessandrose...@linux.com>
wrote:
> The latest Bryan wrote makes me wonder what he thinks is the best for lines
> like this:
>
> Content of /, /boot/ , and /lib/modules/
>
> Is it all right the way it is, or should it become:
>
> /, /boot and /lib/modules
>
> (/boot I level dir, /lib/modules well-known dir) or maybe this?
>
> /, /boot and /lib/modules/
>
> (/boot I level dir, /lib/modules just some dir)
>
If I was aiming for both context and consistency, I think I would aim for
the following ...
- In the context of a directory, use a trailing slash (/), even for TLDs
- In the context of a TLD or mount, use the established name without one
E.g.,
Know the purpose of these top-level directories (TLDs)
/bin, /boot, /etc, /lib, /sbin, /usr, /var
v.
Understand the contents of these directories for the kernel
/, /boot/, /lib/modules/
Neither do I have strong opinions about it.
>
If anyone can make a case for context and consistency, I will support it.
The only thing I care about is nomenclature that ensures context is not
lost and consistency is maintained as best as possible.
The only time I take issue with things is when it removes context and
reduces consistency. It's one of my complaints about exam questions as
well, the difference between a "critical thinking" question and a "trick
question."
I agree they are both useless and "unpretty".
>
The elipsis (..[.])?
Or something else?
Elipsis, and other continuation characters, are unnecessary to refer to
directory structure.
Although there are a few cases where things can be ambiguous. Take IPv4.
Does 192.168. = 192.168.0.0./16? Or just a prefix to a plausible, specific
IP in the range/subnet?
This was addressed very well in IPv6 with the single colon (:) v. double
colon (::) nomenclature. The former means a prefix -- e.g., fe80: -- with
optional subnet -- e.g., fe80:/64. The latter specifically means elipsis
-- e.g., fe80::[/64] -- and can even be appended to be a specific address
(elipsis between values) -- e.g., fe80::ea39:35ff:fe6:f750[/64].
One of the few times elipsis really matter is when you're trying to convey
the option to use plural in commands. E.g.,
mount [options] (blkdev) (mntdir)
umount (mntdir) [(mntdir)..]
-- bjs
DISCLAIMER: That is all, of course, when we're not talking about a Miami
NBC affiliate (and, subsequently, MSNBC) quoting a neighborhood watch
captain, leaving out the 911 dispatchers question, and not using elipsis to
convey the question from the latter, in between two statements of the
former. As I said, never take away context, which only increases ambiguity.
/me (lifetime Sanford-Oviedo resident) runs ;)
--
Bryan J Smith - http://www.linkedin.com/in/bjsmith
_______________________________________________
lpi-examdev mailing list
lpi-examdev@lpi.org
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
