Remeber the band Skid Row, who JBJ took under his wing, took on tour, promoted, then stiffed for every penny they earned?
When they tried to get their money JBJ turned nastier still and threw a heap of litigation at them. I think the Skid Row singer is still forbidden to talk about JBJ in interviews.
But if you number each player, send them out, and expect them to be returned, then by identifying the missing or broken players you could pretty much work out who it was that smashed their player open and put the music on P2P.
Isn't it true that most lost songs, lost sketches, lost stories etc. are lost for a reason?
Even hard-core Python fans must surely admit that a lot of crap made it into a lot of episodes, and these sketches obviously weren't good enough even to get in ahead of those.
Face it chaps. It will suck harder than those lost Beatles songs that kept turning up. And that's HARD.
I was waiting for the typical "stop whining and do something about it" AC. I don't want to just "not use it". I like GNOME, and I want to help make it better.
As I said, what I just wrote was a summary of my first impressions, and was the first step in making a list of the faults I've found.
I don't yet have enough exact details to file bug reports, I don't want to report something as a bug which is actually down to me having built it incorrectly or not understanding how something should work.
I take quite a lot from the Open Source community, and I do like to help out where I can.
I've spent the best part of today building GNOME 2 on Solaris.
I've got a fast machine, so compile time wasn't much of an issue, but there are just so many packages, and finding the dependencies is a fun piece of detective work in itself.
KDE has *big* packages that take forever to build, but you can at least kick them off and leave them to it. The GNOME build is much more involved, not least because, on Sol at least, many of the packages need some gentle persuasion before they'll work. Generally it's just popping -lintl or somesuch into the LD_ADD Makefile line, though a couple of others were more involved.
But is it worth it? So far I'd have to say no. GNOME 2 looks just like GNOME 1, but I liked the way GNOME 1 looked. It seems neither quicker nor slower, and though it's maybe marginally snappier than KDE it's hard to call.
But those crashes! I can't open a Nautilus window without a segfault.It's currently stuck in a loop where it keeps trying to open my $HOME and segfaults every time, then tries to carry on where it left off ad infinutum.
A couple of the control centre applets have crashed on me. A cursory look around GNOME db bombed on most operations.
That's only two or three apps though. What about all the other goodies? Well, for something which professes to be a desktop environment, isn't GNOME 2 awfully sparse? It has the Gimp, it has Gnumeric, it has, err, an xterm. KDE throws in, among many, many other tools. mail, news, and a browser. I know I could get Evolution, Pan and Galeon (if I could get Galeon to build on Solaris, which I can't) but have these been ported to GTK 2 yet? If they have then it's not been well publicised.
Other initial gripes are that the window list applet doesn't work, the control centre seems to have vanished, I haven't yet successfully imported *anything* into Gnumeric, and crashes, crashes, crashes!
I really didn't want to be negative, but as yet I can draw so few positives from GNOME 2. Maybe it's just teething troubles with the Solaris port, but given Sun's supposed involvement that's hardly an excuse.
Maybe I'm missing something, and I understand that the internal architecture has been substantially improved, a change which will pay off big in the future, but from the outside GNOME 2 really looks like a step backwards. I'm hugely disappointed.
My tips for becoming a good scripter, which I think is *essential* for a good Unix admin. (BTW my shell of choice is always Korn, pref. ksh93)
Remember that shell is a proper programming language. I use loops and stuff on the command line all the time - not just in scripts.
Don't use awk when you can use cut etc. etc. You will learn a lot about scripting by trying to be efficient.
Learn how to use sed and vi *properly*. If you use vim, vim.sourceforge.net has loads of useful tips.
Learn Korn shell's ${!}, ${#}, ${x:y:z} type constructs.
Don't depend too much on OS (especially Linux) specific commands. It can make you lazy and you can look like a klutz when you have to use a different Unix.
Sensible use of functions can simplify large shell scripts enormously.
Don't be afraid of creating and using new file descriptors - they can be invaluable.
Become a regex guru.
On the command line, remembering that $_ is the final argument of the last command saves a ton of typing.
To get yesterday's date use TZ=GMT+24 date (assuming you're on GMT)
lsof is an incredibly useful tool - learn it and carry a copy around with you.
For showboating, nothing impresses the uninitiated like proficient use of a line editor.;-)
A function I often use in scripts which produce a lot of output is this;
underline() {
echo $* | sed -e 'p;s/./=/g' }
which easily produces nice, clear underlined headings.
A neat but not particularly useful Korn shell trick, (don't know if it works in bash) is
cat </dev/tcp/127.0.0.1/xx
which lets you read output from port x on the local host.
Other stupid tricks are things like using echo * instead of ls, and all the "funnies" like drink bottle; opener.
Who the hell do Sun think they are? What gives them the right to charge money for a product they've developed? Especially when Linux does everything Solaris does but for free and at least ten million times better.
I hereby demand that to atone for this insulting slap in the face to RMS and 1337 bedroom haX0rs everywhere, Sun place all code they've ever written under the GPL
To watch a two hour kids film? Did you all spend the rest of the day laughing chocolate milk through your noses while you quote The Life Of Brian to each other?
Slashdot Mirror
err.. the one with the T&A?
Technically completely wrong and modded up as "informative".
Sounds like one more reason why BSD is dying... ;-)
Remeber the band Skid Row, who JBJ took under his wing, took on tour, promoted, then stiffed for every penny they earned?
When they tried to get their money JBJ turned nastier still and threw a heap of litigation at them. I think the Skid Row singer is still forbidden to talk about JBJ in interviews.
Like the guy who made Bag End out of Lego. That fucking mattered...
He'd build a gigantic monument to his 1337 c0d1n6 5k!llz
Each step more desperate than the last.
First we have an adult male (I think that's a fairly safe bet) with an unhealthy obsession with Tolkein.
Second, this person also still plays with Lego.
Third, he makes a hobbit hole out of Lego.
Next, he photographs it for his website.
Someone stumbles across said site, and thinks "Wow that's really cool! The guys on Slashdot will love this!" and he sends it in.
One of the Slashdot editors thinks "Wow! That is *so* cool! I'll put it on the front page!"
I spend five minutes of my life, that I can never have back, pointing this out.
This, people, is why computer geeks get laughed at.
But if you number each player, send them out, and expect them to be returned, then by identifying the missing or broken players you could pretty much work out who it was that smashed their player open and put the music on P2P.
Isn't that why they do it?
I hope they fine them *so much*. A bunch of losers trying to be funny using a lame-assed idea they got from an Internet chain letter.
Not so hilarious when a big fat $1000 fine lands on the doormat are you?
Isn't it true that most lost songs, lost sketches, lost stories etc. are lost for a reason?
Even hard-core Python fans must surely admit that a lot of crap made it into a lot of episodes, and these sketches obviously weren't good enough even to get in ahead of those.
Face it chaps. It will suck harder than those lost Beatles songs that kept turning up. And that's HARD.
No, the only thing worse than a Python geek is a combined Linux and Python geek.
And wear a glove so it feels like someone else is doing it.
Other pedants may spot the deliberate mistake. ;-)
Love of money is the root of evil. Introducing evil breaks the proof.
To do that they'd have to go out, and quite possibly interact with real people.
I was waiting for the typical "stop whining and do something about it" AC. I don't want to just "not use it". I like GNOME, and I want to help make it better.
As I said, what I just wrote was a summary of my first impressions, and was the first step in making a list of the faults I've found.
I don't yet have enough exact details to file bug reports, I don't want to report something as a bug which is actually down to me having built it incorrectly or not understanding how something should work.
I take quite a lot from the Open Source community, and I do like to help out where I can.
I've spent the best part of today building GNOME 2 on Solaris.
I've got a fast machine, so compile time wasn't much of an issue, but there are just so many packages, and finding the dependencies is a fun piece of detective work in itself.
KDE has *big* packages that take forever to build, but you can at least kick them off and leave them to it. The GNOME build is much more involved, not least because, on Sol at least, many of the packages need some gentle persuasion before they'll work. Generally it's just popping -lintl or somesuch into the LD_ADD Makefile line, though a couple of others were more involved.
But is it worth it? So far I'd have to say no. GNOME 2 looks just like GNOME 1, but I liked the way GNOME 1 looked. It seems neither quicker nor slower, and though it's maybe marginally snappier than KDE it's hard to call.
But those crashes! I can't open a Nautilus window without a segfault.It's currently stuck in a loop where it keeps trying to open my $HOME and segfaults every time, then tries to carry on where it left off ad infinutum.
A couple of the control centre applets have crashed on me. A cursory look around GNOME db bombed on most operations.
That's only two or three apps though. What about all the other goodies? Well, for something which professes to be a desktop environment, isn't GNOME 2 awfully sparse? It has the Gimp, it has Gnumeric, it has, err, an xterm. KDE throws in, among many, many other tools. mail, news, and a browser. I know I could get Evolution, Pan and Galeon (if I could get Galeon to build on Solaris, which I can't) but have these been ported to GTK 2 yet? If they have then it's not been well publicised.
Other initial gripes are that the window list applet doesn't work, the control centre seems to have vanished, I haven't yet successfully imported *anything* into Gnumeric, and crashes, crashes, crashes!
I really didn't want to be negative, but as yet I can draw so few positives from GNOME 2. Maybe it's just teething troubles with the Solaris port, but given Sun's supposed involvement that's hardly an excuse.
Maybe I'm missing something, and I understand that the internal architecture has been substantially improved, a change which will pay off big in the future, but from the outside GNOME 2 really looks like a step backwards. I'm hugely disappointed.
Sorry.
...where does that put BSD?
You're right, of course. That's why I pointed out at the top of my post that I use ksh. ;-)
Sun have been pushing diskless and dataless clients for as long as I can remember.
Wouldn't it be hypocritical for them *not* to use them?
My tips for becoming a good scripter, which I think is *essential* for a good Unix admin. (BTW my shell of choice is always Korn, pref. ksh93)
;-)
/dev/tcp/127.0.0.1/xx
Remember that shell is a proper programming language. I use loops and stuff on the command line all the time - not just in scripts.
Don't use awk when you can use cut etc. etc. You will learn a lot about scripting by trying to be efficient.
Learn how to use sed and vi *properly*. If you use vim, vim.sourceforge.net has loads of useful tips.
Learn Korn shell's ${!}, ${#}, ${x:y:z} type constructs.
Don't depend too much on OS (especially Linux) specific commands. It can make you lazy and you can look like a klutz when you have to use a different Unix.
Sensible use of functions can simplify large shell scripts enormously.
Don't be afraid of creating and using new file descriptors - they can be invaluable.
Become a regex guru.
On the command line, remembering that $_ is the final argument of the last command saves a ton of typing.
To get yesterday's date use TZ=GMT+24 date (assuming you're on GMT)
lsof is an incredibly useful tool - learn it and carry a copy around with you.
For showboating, nothing impresses the uninitiated like proficient use of a line editor.
A function I often use in scripts which produce a lot of output is this;
underline() {
echo $* | sed -e 'p;s/./=/g'
}
which easily produces nice, clear underlined headings.
A neat but not particularly useful Korn shell trick, (don't know if it works in bash) is
cat <
which lets you read output from port x on the local host.
Other stupid tricks are things like using echo * instead of ls, and all the "funnies" like drink bottle; opener.
I am. It rocks.
Who the hell do Sun think they are? What gives them the right to charge money for a product they've developed? Especially when Linux does everything Solaris does but for free and at least ten million times better.
I hereby demand that to atone for this insulting slap in the face to RMS and 1337 bedroom haX0rs everywhere, Sun place all code they've ever written under the GPL
To watch a two hour kids film? Did you all spend the rest of the day laughing chocolate milk through your noses while you quote The Life Of Brian to each other?
Some of you guys really live the wild life.
It was hardly a documentary, was it?