Linux Action Show Returns 61
BJ writes "The Linux Action Show, the Linux-podcast to end all Linux-podcasts, is returning with their 11th season after over 7 months off the air. Kicking it all off with a live streaming event this Saturday at 5pm. Topics are set to include: Maemo/Moblin merging into Meego, Open Source Nividia drivers with 3D, KDE 4.4 and much, much more."
Lack of professionalism (Score:5, Insightful)
When I got into the whole podcast thing, I downloaded basically everything that had to do with either mobile tech, Apple and Linux. To my surprise, most Linux-related podcasts are really, really bad. The quality was often lacking in almost every area, be it pacing, sound quality, speakers, intro/outro, interviews you name it. This all in sharp contrast with podcasts that are related to mobile news and Apple or iPhone.
So I'm very interested in this (for me new) podcast, but it better have at least some semblance of quality.
Shell syntax lesson (Score:3, Insightful)
> apt-get remove me & I shall become stronger than you can possibly imagine...
Uh, fail.
Why do people talk like this? It's so tacky.
The command is:
apt-get remove me && I shall become stronger than you can possibly imagine...
I don't know if you made an HTML fail or a shell fail, but either way, you botched it. Having two ampersands prevents the race condition and preserves the meaning of the statement; in this context, and means iff.
No, I said what I meant. (If I had meant to put two ampersands in there, why would I be talking about asynchronous jobs and race conditions?)
See, if I use the version of the command that accurately reproduces the meaning of the sentence instead of getting it wrong, then that's not much of a joke. Maybe you thought my joke wasn't funny anyway - that's OK, they're not always funny. But that line of dialogue could actually have either meaning. "and" could mean "if you do this, then this will occur", or it could just mean that two unrelated things are to take place. ("Do the dishes and I'll go take a nap") In the original line from Star Wars I think there was an "if" in that sentence - but the line as stated in this thread could take either meaning, depending on context.
The ampersand shell syntax originally was infix: "cmd1 & cmd2" meant "run cmd1 and cmd2 concurrently". This predates job control, I believe, and I think the shell waited until both processes exited before returning. Nowadays you can still say "cmd1 & cmd2" but in Bash, at least, the meaning is a bit different. "cmd1&" is run as a background job, and "cmd2" is run as a foreground job. The ampersand now acts as a command separator, in other words. With the current meaning, the syntax really is a suffix to a command, even if another command follows it - so reading it as "and" is now a bit unnatural, I guess... But originally there was a very good reason why they used the ampersand for that syntax, and that's why I still read "cmd1 & cmd2" as "cmd1 and cmd2".