How is this different from the canceled Ares? Or they just trim out the LEO variant?
They painted it white.
It may seem flippant, but this comment is pretty close to the money. SLS is indeed the zombie version of Ares V with some relatively minor alterations.
If this is not correct perhaps you should educate NASA and while you're at it let me in on how to properly express 70 metric tons using the abbreviated form.
The SLS will launch between 70 Mg (7e4 kg) and 130 Mg (1.3e5 kg).
Looking at my list of SI symbols, I believe that NASA are claiming SLS will launch 70-130 milli-Teslas...
This is also a common problem with spacing: it's tempting to think, we have N passengers an hour and run a bus every 10 minutes, but N/2 totally fit in a bus, so we could really improve our finances if we just ran a bus every 30 minutes instead. But when the bus runs every 30 minutes rather than 10 minutes, a lot fewer people take it.
Doesn't matter. If you nominally run the bus every 10 minutes, what really happens is every half-hour, three buses come by at once.
"We like to drive in convoys, we're most gregarious!"
conclusion:
it's pretty but it's not exactly the same as GNOME 2.x so I don't like it, and I can't be bothered to type trivial questions into Google.
FTFY.
Except with a major difference: Bazaar gives you the ability to have both checkouts share the same database, so it doesn't take up twice the amount of space. Git doesn't let you do this -- you'll have to create two full copies of the repository. (Ironically, this accusation is often made towards Bazaar by people who haven't heard of shared repositories.)
git does allow you to do this, with plenty of flexibility: see man git-clone. Specifically, if cloning a git repository on the same filesystem, the common data is automatically shared using hard links (don't forget that all entries in a git repository are immutable, so this Just Works); additionally, you can use some combination of the --reference, --shared or --no-hardlinks options to control exactly how cloning should occur.
Perhaps it would have been better to say "I don't think git allows you to do this" rather than "git doesn't let you do this".
Use `git describe':
[peter@harrington gaf (master)]$ git describe
1.7.1-20110619-169-gc9d4f66
This returns a string containing the most recent tag on the branch (1.7.1-20110619), the number of commits since that tag (169), and the first seven hexadecimal digits of the commit SHA-1 (c9d4f66).
1. If you even suggest for a second that systemd isn't awesome, you will hear from people (for example.... you) who says it's great, without addressing any concerns that system admins actually have.
Mainly because said concerns tend to boil down to "Waaah, it's different." Oh no.
2. The command line interface is annoying... it's even worse than the problems we have with SMF on Solaris 10+. Following the original threads about it, you can tell Lennart has no idea what people actually do with the command line. systemd calling $MORE? Hasn't anyone ever used expect?
"Annoying" is an opinion. Could you please link to said threads?
3. They want to roll cron and inetd into it... for no reason that I can see. Vixie cron and xinetd both work great last I checked. This seems to be bacause that's what MacOS X does with launchd, not for any real reason.
There are some advantages, such as per job/per request cgroups to make sure that all processes get cleaned up correctly. I'm not particularly bothered either way. Note that "in systemd" doesn't mean "in PID 1".
4. Doesn't socket activation require changes to daemons?
It does. However, you don't need to use socket activation -- "classic" forking services can be used just fine. Obviously, yes, if you want all the advantages of systemd, daemons do need to be modified to receive their sockets from systemd.
5. D-Bus dependency. On my init system. Sounds awesome, where do I sign up. systemctl actually didn't work at first on my F15 box because... I don't run dbus (standard X11 window manager, I don't generally use Gnome or KDE, lucky me.)
Some sort of RPC was needed for communication between systemctl and PID 1. TBH I would rather systemd used a solution that's already widely used in the Linux desktop, is well-maintained and robust, rather than Lennart rolling his own NIH version. But maybe that's just me. It doesn't seem like an unreasonable design decision to me. What solution would you prefer?
6. Optimizing for a problem most Linux boxes don't have... reboot speed and dependency resolution, which really sounds like something I do as little as possible. I run 100s or 1000s of boxes... reboot speed is rarely my concern... my boxes spend more time in POST then they do mounting filesystems and starting sshd these days. Sounds like a laptop problem to me.
As far as I can tell, systemd is also optimised for ensuring that login sessions and daemon processes are correctly & fully cleaned up (for example, if you're rebooting apache, systemd will make sure all the processes apache forked are terminated -- something SysV init can't do).
7. No separate
"systemd itself is actually completely fine with
Gah, I don't even run systemd myself and I seem to know more about it than most people commenting on this article...
Before PulseAudio it wasn't possible to turn on a bluetooth headset and have any audio that was playing through your speakers automatically start going to the headset instead.
And that was a fundamental design flaw in Alsa (rather than just missing drivers), and it could only be remedied by inventing a whole new sound daemon / system and putting it on top of Alsa?
In a word, yes.
systemd is fine. Out of interest, what exactly is your problem with it, other than it's not SysV init?
What does PulseAudio-on-ALSA accomplish that straight ALSA cannot? Assuming a non-null answer to that, how many users really need that functionality to justify including PulseAudio as the default configuration for major distributions?
At the risk of repeating myself:
For my friends who use Linux, the first thing I do whenever a new distro is installed is to check if it is using PulseAudio. If so, I remove it and replace it with ALSA. Suddenly issues related to audio playback go away and everything just magically works. Oh and they easily have a proper mixer without jumping through hoops, too, which is handy considering some of them are using 5.1 surround sound and/or bluetooth headphones.
So, tell me. How, using ALSA, do you turn on a pair of BT headphones and redirect sound from running apps to them?
I too had problems with PA when it was initially introduced, but now I haven't had any problems with it in literally years. These days it Just Works, and I've used some of its nifty features from time to time. To claim that it doesn't solve any relevant problems or that raw ALSA should be the default is completely bogus, TBH.
If ALSA were a barely-functional, poorly designed sound system...
It is.
cgroups -> jails
What on earth are you talking about? They have completely different aims and functionality!
How do you get a spacex dragon to Mars orbit in the first place?
Using the (collosal) SpaceX Falcon Heavy launch vehicle. I know that R'ing TFM is not fashionable here, but seriously...
Oh, and I also use Okular on Windows. It works quite nicely.
One of the chief duties of the mathematician in acting as an advisor... is to discourage... from expecting too much from mathematics. -- N. Wiener
