Quiche eaters

[Wojciech Derechowski]

Trying to make my SO life a little easier I went to see what an install of the
most popular media centre would be like and read the build guide. In fact I
read half a page and I quote:

Several different strategies are used to draw your attention to certain pieces
of information. In order of how critical the information is, these items are
marked as a note, tip, or warning. For example:

NOTE: Linux is user friendly... It's just very particular about who its friends
are. TIP: Algorithm is what developers call code they do not want to explain.
WARNING: Developers don't change light bulbs. It's a hardware problem.”

Endquote. Given that this build guide is supposed to cover FreeBSD the note
example is difficult to understand, the tip example is easy and obviously false,
and the warning example should read 'WARNING: Quiche eaters! Avoid at any cost.'

WD
--
Who is Entscheidungs and what is his problem?

[Mans Nilsson]

Post by Wojciech Derechowski
most popular media centre

The concept of "networking" that %DEVLOPR of said systems can grasp
is limited to "everybody has one NAT network behind a bad plastic
box." Also, they swear by the moses-stone-tablet-truth of "it is
impossible to pass packets through a router unless there is a port
forwarding set up".

Being a network Operator I naturally do not want filthy spyware boxen on the
same network as reasonably controlled servers, and both kinds of devices
must be isolated from various greasy-screened portable computing devices
without proper keyboards.

The amount of work that has been put into limiting the media centre
software into not doing simple things like serving a file to someone from
another subnet is impressive. And nobody understands what I'm talking
about, more than "oh yes, there was some lunatic greybeard 2 years ago
on the forum who said incomprehensible things like 'access list´ and
´routing table´ . We ignored him too."

Lusers clobbering together shiny crap.

[Peter H. Coffin]

Post by Mans Nilsson
The concept of "networking" that %DEVLOPR of said systems can grasp
is limited to "everybody has one NAT network behind a bad plastic
box." Also, they swear by the moses-stone-tablet-truth of "it is
impossible to pass packets through a router unless there is a port
forwarding set up".

THe happiest network I ever saw was managed by a pufferfish-OS box with
about six NICs in it. It handled routing and mail, and passed other
traffic off to specific departments. Even the manager for that box was
kind of surprised how little traffic actually needed bridging between
the internal networks. That's what sold me not-flat internal networking
space for anything more than trivial/toy/home networking.

[Chronos]

On Fri, 24 Aug 2018 08:09:33 -0000 (UTC)

Post by Mans Nilsson
Also, they swear by the moses-stone-tablet-truth of "it is
impossible to pass packets through a router unless there is a port
forwarding set up".

Which is why we now have the distinct possibility of PT-ANG second class
netizens instead of the big, scary hex stuff that "can't be stealthed"
with a few lines of sverjnyy directives despite the fact that most of us
have been doing just that for nearly two decades.

Post by Mans Nilsson
Lusers clobbering together shiny crap.

The very definition of Io[T|S]. In fact, of anything starting with Io,
Pybhq or ending with aaS. The proponents of these are also the people
who like to throw out words like "synergy" or "leverage" once in a
while to make sure we're all awake. Well, sunshine, I am awake but if
you again misuse that word in that context in my presence after this
warning it'll be rather a long time before you experience such a state
of wakefulness.

It usually takes them about an hour to translate that into luserese,
too, by which time all the witnesses have long since buggered off,
flushed their short-term memory of the pointless meeting and a complaint
about workplace threats would go nowhere.