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.
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.
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.
It's not known whether the universe was created by the Big Bang, or the Invisible Pink Unicorn, but if we assume the Big Bang model, then I don't see how there can be any "before" it.
You'd normally just wait for a router advertisement (ICMPv6) message arriving for the "all link-local nodes" multicast address (ff02::1). If you don't feel like waiting for one, send a router solicitation to the "all link-local routers" multicast address (ff02::2), the router(s) will respond with router advertisements (possibly via unicast in this case, not sure). The router advertisement contains the (64 bit) interface identifier; the router is then reachable on the link-local unicast address fe80::.
In unix, you can query information about all this after the fact using ndp(8).
Oh noes, an integer in a database, on a site that is bordering on the irrelevant anyway. I certainly see how accidentally losing karma could completely destroy lives here. Sheesh.
It's thus the most dangerous kind of comment to post... and my favorite.
Same here, and for some reason I've been at Karma: Excellent for years; high UID and questionable username notwithstanding. And I don't even give a shit about it. You might want to try that.
That said, I do recognize your signature and I generally like your comments. Most of them, anyway. Keep it up, and care less about karma.
Slashdot Mirror
You should try and read the link in the comment you replied to
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.
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.
It might be the fact that the BSDs already have a mature and sound dependency-based init system.
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.
Thanks for the headache
But this is big. It's right there in TFA.
Now we remap the damn key to produce an Escape keysym.
Cardboard? Fucking casual.
The correct solution is to glue a drawing pin onto the keycap, upside down.
before the Big Bang
bzzzzt.
It's not known whether the universe was created by the Big Bang, or the Invisible Pink Unicorn, but if we assume the Big Bang model, then I don't see how there can be any "before" it.
[...] on link-local unicast address fe80::<interface identifier>.
You'd normally just wait for a router advertisement (ICMPv6) message arriving for the "all link-local nodes" multicast address (ff02::1).
If you don't feel like waiting for one, send a router solicitation to the "all link-local routers" multicast address (ff02::2), the router(s) will respond with router advertisements (possibly via unicast in this case, not sure).
The router advertisement contains the (64 bit) interface identifier; the router is then reachable on the link-local unicast address fe80::.
In unix, you can query information about all this after the fact using ndp(8).
HTH
I hope you don't mean on the client end, because that would make a ridiculous claim.
Or on the server end, because that, well, would make a ridiculous claim.
I'm not against offering a browser-or-whatever-based GUI, I just find it a stretch to call that a "small and lean" firewall.
small and lean firewall
improvements to the GUI
Uh-huh.
got modded funny and troll you lost karma.
Oh noes, an integer in a database, on a site that is bordering on the irrelevant anyway. I certainly see how accidentally losing karma could completely destroy lives here. Sheesh.
It's thus the most dangerous kind of comment to post... and my favorite.
Same here, and for some reason I've been at Karma: Excellent for years; high UID and questionable username notwithstanding. And I don't even give a shit about it. You might want to try that.
That said, I do recognize your signature and I generally like your comments. Most of them, anyway. Keep it up, and care less about karma.
I kind of wish Slashdot has Reddit's threading features, where you'd be notified when replies were made. I think it encourages active discussion.
You do realize that you can get email for replies, right? It's in the account settings.
The sliders above the comment section.
Move them.
but it's not worth you paying for my time to do so when we can replace it for around the same cost.
You realize that doesn't make sense, right? Why should they care who they're paying, if it's the same cost...
For instance, the law of gravity says that things fall down
Oh please.
I'm an engineer
A "software engineer" by any chance?
It is fine for it to travel through a gate, a firewall inspect whether its source address has a pass or not
Finally someone who actually understands what they're talking about rather than just making loud, uninformed claims.
the exec + is asking for trouble. exec \; is asking for slow.
the correct way is, as you mentioned, -print0 | xargs -0
for f in python perl shell script; do printf '%s: %s\n' "$f" "$(find /{,usr/{,pkg/,local/}}*bin -type f -print0 | xargs -0 file | grep -Fi "$f" | wc -l)"; done
python: 11
perl: 39
shell: 260
script: 314
I wrote my sig in perl
Considering this suggestion I'm glad to see that you did improve a bit.
...he was making a game reference, and what he got are unforeseen consequences. Sounds about right to me.