Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Re: The white in your eyes (Score 1) 219

Fitting in with other people is one of the most important aspects of most jobs.

I keep hearing this. And not believing it.

The most important part of a job is being able to do the job.

Nothing GREAT comes from "just fitting in". If you can't handle DOING THE JOB then screw you. You suck. Live with it.

Comment Re:Solution looking for a problem (Score 1) 151

How big a market is this "defensive" drone problem? Seems more likely the market is bullies chasing down innocent drones

Seems like you are a child who lacks a bass understanding of how drones
are used in the real world.

If you ever leave your mother's basement you are in for a shock, son.

The treble with that remark is that it's totally off-key.

Submission + - Book Review: "FreeBSD Mastery: Storage Essentials", by Michael W. Lucas (amazon.com) 1

Saint Aardvark writes: (Disclaimer: I received a free copy of this book for review. Disclaimer to the disclaimer: I would gladly have paid for it anyway.)

If, like me, you administer FreeBSD systems, you know that (like Linux) there is an embarrassment of riches when it comes to filesystems. GEOM, UFS, soft updates, encryption, disklabels — there is a *lot* going on here. And if, like me, you're coming from the Linux world your experience won't be directly applicable, and you'll be scaling Mount Learning Curve. Even if you *are* familiar with the BSDs, there is a lot to take in. Where do you start?

You start here, with Michael W. Lucas' latest book, "FreeBSD Mastery: Storage Essentials". You've heard his name before; he's written "Sudo Mastery" (which I reviewed previously), along with books on PGP/GnuPGP, Cisco Routers and OpenBSD. This book clocks in at 204 pages of goodness, and it's an excellent introduction to managing storage on FreeBSD. From filesystem choice to partition layout to disk encryption, with sidelong glances at ZFS along the way, he does his usual excellent job of laying out the details you need to know without every veering into dry or boring.

Do you need to know about GEOM? It's in here: Lucas takes your from "What *is* GEOM, anyway?" (answer: FreeBSD's system of layers for filesytem management) through "How do I set up RAID 10?" through "Here's how to configure things to solve that weird edge-case." Still trying to figure out GUID partitions? I sure as hell was...and then I read Chapter Two. Do you remember disklabels fondly, and wonder whatever happened to them? They're still around, but mainly on embedded systems that still use MBR partitions — so grab this book if you need to deal with them.

The discussion of SMART disk monitoring is one of the best introductions to this subject I've ever read, and should serve *any* sysadmin well, no matter what OS they're dealing with; I plan on keeping it around for reference until we no longer use hard drives. RAID is covered, of course, but so are more complex setups — as well as UFS recovery and repair for when you run into trouble.

Disk encryption gets three chapters (!) full of details on the two methods in FreeBSD, GBDE and GELI. But just as important, Lucas outlines why disk encryption might *not* be the right choice: recovering data can be difficult or impossible, it might get you unwanted attention from adversaries, and it will *not* protect you against, say, an adversary who can put a keylogger on your laptop. If it still make sense to encrypt your hard drive, you'll have the knowledge you need to do the job right.

I said that this covers *almost* everything you need to know, and the big omission here is ZFS. It shows up, but only occasionally and mostly in contrast to other filesystem choices. For example, there's an excellent discussion of why you might want to use FreeBSD's plain UFS filesystem instead of all-singing, all-dancing ZFS. (Answer: modest CPU or RAM, or a need to do things in ways that don't fit in with ZFS, make UFS an excellent choice.) I would have loved to see ZFS covered here — but honestly, that would be a book of its own, and I look forward to seeing one from Lucas someday; when that day comes, it will be a great companion to this book, and I'll have Christmas gifts for all my fellow sysadmins.

One big part of the appeal of this book (and Lucas' writing in general) is that he is clear about the tradeoffs that come with picking one solution over another. He shows you where the sharp edges are, and leaves you well-placed to make the final decision yourself. Whether it's GBDE versus GELI for disk encryption, or what might bite you when enabling soft updates journaling, he makes sure you know what you're getting into. He makes recommendations, but always tells you their limits.

There's also Lucas' usual mastery of writing; well-written explanations with liberal dollops of geek humour that don't distract from the knowledge he's dropping. He's clear, he's thorough, and he's interesting — and that's an amazing thing to say about a book on filesystems.

Finally, technical review was done by Poul Henning-Kamp; he's a FreeBSD developer who wrote huge parts of the GEOM and GBDE systems mentioned above. That gives me a lot of warm fuzzies about the accuracy of this book.

If you're a FreeBSD (or Linux, or Unix) sysadmin, then you need this book; it has a *lot* of hard-won knowledge, and will save your butt more than you'll be comfortable admitting. If you've read anything else by Lucas, you also know we need him writing more books. Do the right thing and buy this now.

Comment Re:strawman; nobody's asking him to be "PC" or "ni (Score 1) 361

Your first response doesn't convey the additional problem the way the 2nd one does

What additional problem?

"Hi, I am the busiest man in the free software world, and you just consumed my valuable time with amateur level mistakes. We have a FAQ about this, which you either didn't read or didn't understand, and as a result, my productivity has suffered. Please re-read the contribution FAQ. If you are still confused, send a message to LKML, not to me"

"I've cc'd this response to LMKL so that others don't repeat your mistakes, and so that everyone else is expecting your follow up questions and amended patch"

It's not "abusive" to point out that when people don't do their due diligence, everyone else suffers. Set an expectation of excellence, and expect people to follow it.

Results first. Feelings later.

Comment Re:Don't care? (Score 5, Insightful) 361

Do you have any evidence of this? At all?

Because here's what I see:

Linux has remade the software world in its own image. I'd hardly call that "failing". Real actual super computer companies (e.g. Silicon Graphics) stopped developing their own OS and started shipping Linux.

Microsoft, the arch nemesis of Linux and Open Source, is shipping kernel patches and releasing code under open source licenses.

What does "success" look like to you?

And lest you say "that's just a singular case", we can look at Theo and OpenBSD. OpenBSD has been wildly successful, both as a BSD fork, but also in its broader mission to cultivate a software culture of excellence and correctness, with results that speak for themselves.

Linux and OpenBSD are two of the oldest open source projects around, with two pretty intense personalities at the helm.

I see no evidence to support your claim whatsoever.

Comment Frustration (Score 1) 361

There's this idea in the US that you are never allowed to hurt anyone's feelings.

The problem with that is that people are irrational, oversensitive, and cannot control themselves. Interacting with such fragile daisies is like tiptoeing through a minefield.

It is not, to me, a foregone conclusion that assertive people should tolerate having to deal with sensitive people. That is the prevailing dogma in US business, but it's not clear why that should be the case.

The meta response to this entire conversation space should be "stop bothering me with your bullshit and submit some fucking code"

Comment Re:no thanks (Score 1) 172

Caller: "I didn't say I wanted to use less energy, dumbass, I said I wanted you to charge me less for the energy I *do* use!"

That's an illogical reaction. Gas stations won't charge you less for using the same amount of gas. Your cable bill won't go down when you have the same channel package. (Yes, many of us want a la carte, but that's the moral equivalent of "use less electricity".)

It's an artificial scarcity used to inflate value. Generating "just enough" electricity, rather than "more than enough", when you are using a nuclear plant, is more about what you do with the heat (do you turn it into electricity, or do you shunt it to the cooling towers, because you can't throw it on the grid), rather than whether or not the heat is going to be relatively constant, unless you are in a changeout cycle.

Thankfully your ala carte cable is coming to pass (i.e. the unbundled ability to get some channels online is now there).

Comment Re:Prepare for more (Score 2) 257

I really do not care if there was revisionist history or not. Japan had shown themselves to be pretty ruthless, and as I recall, they started the whole mess.

Though only after US inflicted crippling economic sanctions on them. I'm not a US basher, but large powers (US, Russia) tend to act like school bullies.. they push you and push you, and then when you push back, it's suddenly "a surprise attack".

Granted, it was a surprise attack, but it should not have come as such.

And by "crippling economic sanctions", you mean we stopped selling them scrap steel for them to use in pursuit of their war on China, where they were attempting to seize territory so that, among other things, they had the ability to mine to produce their own steel.

They were kind of expansionist, empire-building, belligerent asses at the time. A conflict was inevitable, even if we'd enabled them to take China, other areas in Asia, and the Philippines.

Comment Re:no thanks (Score 1) 172

Do you think that energy prices are NOT going up anyway?

That's the great thing about smart meters ... if you are a power company.

You get to work around the PUC tariffed rates by showing that *on average* electricity price haven't actually gone up, while increasing revenue by 20% without having to go back to the PUC and make any concessions to get the tariff changed.

Well, that and you can charge differential rates from what you pay for solar power generated when no one is home during the day to use it. That's a lot harder to do, if you used an electromechanical meter that actually ran backwards when generation exceeded consumption.

Slashdot Top Deals

2.4 statute miles of surgical tubing at Yale U. = 1 I.V.League

Working...