Comment Re:This is what they mean by "point of no return" (Score 1) 273
IIRC, the half life of methane in the atmosphere is around a decade (loosely speaking) but it converts to CO2 in most of its degradation modes (like being eaten by bacteria).
IIRC, the half life of methane in the atmosphere is around a decade (loosely speaking) but it converts to CO2 in most of its degradation modes (like being eaten by bacteria).
But if you make the battery blow up, you can't track the phone anymore.
Why? I'm not considering supporting them, and I'm not considering their opposition, so why should i watch it? I'm sure I could see as bad if I went down to the hospital emergency room and waited for awhile.
I really don't think that snuff fliks add anything of benefit to human society, no matter who does them. What I find most repellant about this thing is that some people want to watch it. All states claim the right to decide when and for what to kill people, and this is just ISIS claiming that they're as good as any other government. (Some governments have decided not to kill people, but they have reserved the right to change their mind.)
The microgrid idea is attractive, and would work. Unfortunately, it appears inherently more expensive and less efficient. This would make it an extremely hard sell. It also decreased central control, so the govt. wouldn't be attracted to it, even if they didn't actually put up roadblocks.
What's broken is this. The initt system assumes:
1) All the subsystems boot quickly 2) None of them need to communicate back and forth about status in complex ways 3) The list isn't too long
There exists lots of users for which one or more of those 3 assumptions are false. If you don't assume those 3 then you would design boot differently.
Take a look at things like OpenRC. It manages a lot of that kind of stuff really really well. I'd much rather have it than systemd.
You got a bunch of "upstarts" who don't know, or don't care, about Linux's roots and want to turn it into something it just never was meant to be
When I was a junior network engineer, I sometimes had to work on (what we now consider ancient) technology such as ATM, Frame Relay and ISDN. I even had my share of IPX/SPX. Back in those days, the experienced network engineers with 20+ years of experience despised Ethernet while complaining about those junior folks who knew nothing about the established technologies. As it turned out, all of them are out of a job now. Bottom line is, when it comes to technology progress, roots are pretty much irrelevant. I don't care if something has been done like this for 1000 years. If we can find a better way to do it, let's do it. The question should be whether or not systemd is progress, or an unnecessary burden. History is irrelevant in this case.
From every experience I've had with systemd, I'd say that it is NOT progress. I don't want every little thing integrated in the manner systemd does.
And frankly, OpenRC is a lot better.
You did oversimplify. There's really no sense in talking about the "extent to which we are contributing" because of various positive feedback loops. I suppose that if you just say "we are a major contributor to global warming" you would on safe ground, but anything finer than that an things get really complicated. Even this article talked about how a warmer ocean causes increased release of methane....which causes a warmer ocean...which... (Well, the article didn't expressly mention that this was a loop. And only one of many.) Fortunately there are also some negative feedback loops...but they don't appear to be as strong. Or perhaps they're just slower. If deformation of the earth's crust (by melting the glaciers that acted as weights holding it down) sets off a chain of volcanos, then we may end up dealing with a global cooling problem.
FWIW, the drying out of western North America has caused deformation of the earth's crust in that area, as the weight of the water has been removed. It's only about (IIRC) 6cm/year, but volcanos have been active in the US west coast that had long been dormant. Probably a coincidence, but do look up the "Deccan Tapps". And remember that we can't yet predict volcanos or earthquakes.
It's true that most distros are committed to using systemd. That doesn't make it a good choice, and it was often a very narrow vote that approved it, because that are lots of things to hate about systemd. Also, a large number of people don't really trust the lead developer. And
I'll probably wait to decide that I won't have anything to do with it for awhile, though. Perhaps it won't turn out to be as much of a blivet as it looks like. But in the meantime I'm going to be checking out alternatives. Just in case. If it's as bad as some have reported, I may be switching to some flavor of BSD.
It actually did need more than just streamlining, e.g. it needed to use multiple processors if available. But systemd seems "a bridge too far". OTOH, I prever grub over either lilo or grub2. Grub gave me enough control and was easy enough to understand for the simple features I wanted to use. Grub2 is inintelligible, and all the readable files say "warning: This file will be automatically overwritten". And lilo didn't give me any control over what what happening.
I'm not deep into systems administration, and I don't want to be. OTOH, I do want to configure my own system to do what *I* want. And what I want is often not what the designers of the software expect, even though it's well within the range of things handled by the software. So I dislike systems that are either too automagic or too inflexible. Systemd is, from all reports, too automagic, and simultaneously too inflexible. So I'm seriously thinking about switching to Gentoo or Slackware. Or even one of the BSDs, though I don't know enough to even guess which one. (I have a desktop orientation, not a server or minimalist orientation, but I need to do some server style jobs. Most Linux systems will handle this easily, but I think that some BSD systmes are too heavily oriented towards server setups.)
The Yellowstone Supervolcano wouldn't split the Earth apart at its seams any more than any of the other reasonable scenarios would. Even the collision that created the moon didn't do that. It might, however, kill off most people in the North American continent. And solve global warming at the same time.
The thing is, there's no real way to predict when, or if, it will go off again. There's some magma filling chambers under it, which has some people worried, but nobody knows whether or not its really significant.
No, most life on earth will survive any reasonable global warming scenario. Civilization surviving is much less certain. So while it wouldn't directly kill us, it might result, indirectly, in 90% of humanity dying. Not, repeat, *not* 90% of life on Earth...unless it resulted in all-out warfare between the mega-powers. All-out nuclear warfare could do that, I suppose.
6 is a bit strong for a foreshock, isn't it? I'm not quite sure.
Clearly it means the stress has shifted to another part of the fault, but is there any reason to believe that the next stress point will be as energetic? The fault I really worry about is the Hayward fault.
The number of UNIX installations has grown to 10, with more expected. -- The Unix Programmer's Manual, 2nd Edition, June 1972