Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:What was the command? (Score 1) 148 148

Real sysadmins

a) think before executing potentially disastrous commands, and therefore tend to not need the rm -i crutch
b) automate the repetitive parts of their jobs, in which rm -i obviously does not make sense
c) don't experiment around on production servers
d) have arranged their systems so that accidentally removing stuff can be recovered from.

Thanks for playing, though

Comment: Re: Hate to be that guy, but Linux (Score 1) 512 512

old tired unix admins that grow weary of typing on the command line all day.

You'd think old unix admins would have figured out at some point that they can automate things, no?

(Hint: it's the very point of the CLI and there's no equivalent meschanism in the GUI paradigm.)

Comment: Re:Dependencies (Score 1) 119 119

So what is a sane init system to do in case of a broken disk? Pretend everything's good and mount its filesystems r/w so that we might get away with starting sshd anyway?
A broken disk is a broken disk. Dropping into a single-user console makes sense because "broken disk" comes in too many machine-indistinguishable flavours for a program to meaningfully take care of and the consequences of "just trying something" could be severe.

If you need this kind of robustness, use a RAID.

Comment: Re:Please explain a passage from the article (Score 1) 143 143

Would it be more correct to say "Spacetime began with the Big Bang"?

That's the general idea, yes, as far as we (don't) understand it. Of course, whether that's true or not is an entirely different issue, but this model at least allows us to explain a few things (e.g. CMB).

Assuming "Spacetime began with the Big Bang", I see no room for reasoning about what came "before" it. Of course, our spacetime might embedded into something else, but that's shifting the question rather than answering it, IMO.

Comment: Re:Dependencies (Score 1) 119 119

The NetBSD init system (which was introduced way back in 2001, and I think ended up being adopted by the other BSDs) has a simple way of solving this. There's a tool called rcorder that parses REQUIRE and PROVIDE lines in each startup script (it's tsort, essentially) and determines the order to run each script. If you wanted to debug something, you could run this yourself and check the output.

Came here to say this.

Work smarter, not harder, and be careful of your speling.