sh_tinh_hair

I've found that holding down two jobs isn't unbearable for short periods of time. You need the right positions, lots of experience in a couple fields and a good resume and references. Small company FT flex/remote SA or devops and SA/TS on call is a good combo, but you need to have a good track record and be honest about your commitments. Security and development remote or flex are also good combinations for this approach. Wouldn't recommend it as a a way of life.

The keywords there are 'typical hardware', but it can get worse. How about 'badly selected' hardware on a short time frame, in situ, waiting for an install and application port process to be performed by non-technical users following a recipe. Proprietary drivers for network and soft raid with a large enterprise linux vendor support and site license basically voided. There are worse things than starting an install,loading storage drivers, creating the lvm partitioning, hup'ing disk druid, installing, rebooting and adding the network driver to initrd, and having to explain and document that manual procedure to the same people who ordered the hardware...but I've forgotten them.

Exactly.

You know I really don't care for a pl that tells me how to do things. I fought python for a long time on a simple issue like indentation. C like syntax is best. RUST is stupid syntactically...surely you've noticed it's a leap. I'd use limbo before Rust.

I don't need to watch a propaganda film to remember how it was. I was there. How old are you?

Understood. Same privilege escalation applies. ..and the syscall chroot is used between systems as a primitive in either os space and semantic.

Selinux MAC is painful coming from DAC and it has bitten me numerous times but depending on your environment and exposure it can be a must have.

I wouldn't run an 'exposed' system that had SELinux support (and decent rules) without SELinux. Not discounting chroot, but given root a lot is possible in a jail.

Apologetics only gets you so far. In this case I don't care for the attempt. Let those who have an interest take advantage and the rest catch as catch can. This marketed approach is badly conceived.

Your suggestions are ideal in terms of training and compatibility with society. I just don't think that they are practical (in the US) right now.

The dysfunctional approach between police and citizens seems to be more manageable and cheaper and makes candidates more numerous. My cynicism is showing though.

This is insightful.

Ran into this sort of thing at a .gov during audits for systems accreditation in 200x. I made the mistake of using 'mitigation' in my documentation and opened up a can of worms with the contracted auditing firm. They should have provided a glossary of weasel words.

Took twice as long to get the system accredited because of a common sense initial approach.

In the 70s when police officers carried a baton and a revolver you'd encounter a lot more talk, diplomacy and second chances. In the age of terrorism and tazers that has become rarer in my experience.

Police officers need to have an 'edge' that is missing in normal people. Normalizing their experience with people and re-humanizing them isn't the best idea for their career and longevity in this day and age. Let them burn out in peace or find a way to cope with their distance from people (usually alcohol, seen that a lot).

I was working at a high school as systems/network administrator using NT 3.5/4., Novell Netware 3,4,5 and SuSE linux 5.x. Doesn't seem so long ago to me.

That's a relatively new concept. Traditional developers didn't understand much about systems design for scalability, redundancy and much less about operational discipline and systems change management (and in my experience many developers still don't).

Firstly: I've administered and designed large CI/CD real world installations for what would be single project scope at Google and those efforts are challenging enough for me.

The book was informative as it contains true to life episodes in a huge (and formative) devops environment. But ,in general, there was nothing that I took away from the Google SRE 'way'...except that I have no desire to work in a huge and hugely rigorous devops environment like the one at Google (though I see it's necessity at that scale).

Under the guise of being creative and solving unique problems you eventually drill down to the reality of a pseudo-religious approach to building,maintaining and administering rapidly changing large systems.

I'd argue that the truly valuable parts of the book for most folks are snippets on the evolution of Google infra, component reuse, design philosophy and lessons learned. These are valuable for any size environment doing any sort of computing.

OsX has always been the alt-users paradise. As a sysadmin and developer I've disliked it from the start. Windows I could use for gaming and when I had to. Linux and FreeBSD are fine for every conceivable use I have d2d.

Trumps election is a symptom of the effects of perpetual war, associated propaganda and globalization in markets and jobs in the US. He is symbolic of peoples frustration with politics, taught jingoism, and nostalgia for a less complicated world.

His selection is also a backlash against a culture too-far: the emphasis on PC thinking and behavior,the new religion of inclusion which older|traditional personalities find to be decadent and repulsive.

You can boycott what is 'American' because of Trump but Trump doesn't care about America.

I guess that is equivalent to 'if it might be broke, break it'?

Exactly what I rail against in Rust. What do you see when you toss a coin friendo?

Dictatorial concepts in PL usually fail pretty badly. Rust may become the textbook example of a good idea too far. I'd certainly never use it or use anything written in it given a choice and/or time to rewrite in anything more accessible.

Led a netware 5 migration from NT4 and NT 3.5 in 1999-2000. Some people then would have disagreed with you. :)

I've used Linux and FreeBSD (desktop|laptop @work/home) for everything since 2002. Within the last five years it really has been a very simple and feature rich environment with acceptable stability for most distributions.

Think if I hadn't started with KDE at that time I would be much more fond of OS X.

Relationship penalty.

You are right. I've long forgotten about read() and write() compat with sockets for very good reason. I don't lump an eventfd into the same IPC category as those mentioned in parent for the semantic(s) reason you mention and also for it's intended usage.

"In particular the most likely explanation for correlation between bad names and bad code is unskilled or inexperienced programmers..."

Totally disagree with this assertion: Laziness and two fingered typing are to blame.

It also tells you how a bunch of common tools will fare against your wonderfully designed solution that is only 'truly' testable by sophisticated methods.

Thanks for whatever it is that you gave me. I don't keep up with nomenclature these days.

Sure it is. It tells you exactly what performance a single threaded application can expect with serial read()s and write()s (and whatever options you choose to invoke dd with) against whatever file source and constraints/conditions are extant at the time. Perfectly valid.

Great analogy.

Only one ipc primitive (fifo) can be used with man 2 read or write. Sysv ipc cannot, sockets (any domain) cannot (unless there is a kernel interface via /proc or another pseudo fs). What is meant by this saying (and the way it is has been used in my experience) is that everything in unix _looks_ like a file. That is usually meant in reference to the C API which has some r[ec]v|read|write|snd type namespace.

My situation is extraordinary regarding the mortgage since I can't deduct it: so tax rate is pretty accurate. The sports car is nicer than the average (approaching supercar) and the SUV is categorized as luxury. Not out of the ordinary in this area.

In order to afford a decent newer house in the suburban beltway (DC) you need to spend 500k+. That's $2200 a month. Personal property tax on a 3 year old SUV and a new sports car is $2700 yearly. Car insurance is > $300 monthly. Car payments >= $1900 month. (college + personal) Loan repayment = $400 monthly. Food and gas + energy >= $600 monthly. State and federal tax + ss take about 45% of gross.

Upper middle class == ~ 170k a year. Welcome to northern virginia.