Why is everyone so keen to bash Enterprise? Seems even a lot of Trek fans just/want/ it to fail.
Okay, so a few episodes have sucked pretty bad, but all in all it's a pretty entertaining show. Decent actors, nice sets and effects, some good stories.
I'm a pretty keen Trek fan, and I don't really care about the inconsistencies with other series: I just what to be entertained for an hour, and Enterprise usually manages to do that.
Now, Voyager, on the other hand. THAT sucked total ass...
you just have to go back twice. On its way back to the future your first self runs over your recently arrived second self, the girl takes pity on you, looks after you, falls for you. Isn't that how it works?
You're all saying what a dork etc he is for getting so het up about this, or for quitting his job, but everyone seems to be overlooking the dorkiest fact of all: HE WAS PRESIDENT OF A LINUX USER GROUP.
He probably just got a girlfriend and has to drive her somewhere on Thursday nights.
I used to love the Amiga. I still have two (A1200 and A4000.) Sometimes I use them, primarily to run Bars and Pipes, and I'm always amazed at how speedy and pleasant they are to use. But, I let it go as a serious computing platform a long time ago.
Like most people here, I originally saw this release as pointless - who would use such a thing when they can use a Unix derivative or a Mac? What a silly OS, with no applications. Then I got round to thinking what I use my computers for.
I run Solaris on my desktop and Linux on my laptop, and all I do with them is web browsing, mail, a bit of coding (mostly web stuff), some graphics stuff, and then just general tinkering. I think the same goes for a lot of other people here.
If I could get a nice stable port of GCC, GIMP, Apache, PHP, an nice browser and a decent mail client, then I could very happily use an Amiga, and I'd have a whole new OS to play with. So why not?
Make a quiet, decent looking off-the-shelf machine running this OS, sell it for a fair price and I for one might be interested.
That's so true. Someone calls me in a public place, I retreat to somewhere where I won't annoy people, and if I can't do that, I speak quietly, and try to keep the length of the conversation to an absolute minimum. Usually I'll just say I'll call them back when it's more convenient for me.
Asshole has such an over-developed sense of self-importance that he thinks his conversation is not only more important than the peace of the people around him, but that the pathetic rabble will be impressed by his long, loud conversation. Or perhaps it's just that so many folk don't have any respect for the people around them.
The thing I really hate about modern phones is that so many have cameras. Take, for instance, the proliferation of twats in pubs and clubs pointing the phone at any half dressed/half attractive woman in sight, aiming up skirts and down tops for the leering benefit of equally twattish friends elsewhere.
I'm talking *very* long term. Working up to sending very large, or multiple, instruments. Things of roughly equivalent size to a person and what they would need to survive. (You could, of course, send multiple craft some unmanned carrying backup systems and supplies.)
I appreciate even that isn't the same, but it's a hell of a lot closer than we are now. You then just have to extend existing technology rather than creating it from scratch. I'm not talking about sending something the size of a TV set here.
If I may use your own analogy, we have a small sub with cameras. Next we build a bigger one with more powerful lights and better arms. Then another, probably bigger still, more powerful, capable of, say, drilling into the sea bed. Then another with a small automated laboratory on board. That might be the size of a car. You're already much closer to being able to build something that might carry a man. You're not there, but you're nearer, and you've done a lot of worthwhile science in the process.
I guess what I'm trying to say is that sending people is only justified when the cost is reasonable, and for the cost to be reasonable most of the technology to do the job must be in place.
Trying to send people now is like building your nuclear sub when we've just mastered the waterproof camera. Building a small manned sub when we're very good at building similar sized unmanned ones is not so unreasonable.
Send orbiters, probes, robots. Make them bigger and more sophisticated as you go along. Send things that take samples and come back. Do this often enough and eventually you reach the limits of what unmanned technology can accomplish, but by then the launching and recovery systems should be so proven and capable that sending a person becomes little more complicated than sending a couple of big packages of instrumentation.
Gradually work towards sending a person and bringing them back by sending lots of expendable things, and bringing them back with stuff for us to study here. Scale up as we go along instead of having one immediate big push. Isn't that sensible?
It's amazing how many people on here have single handedly saved companies, made stock rise 1000%, rewritten legacy applications in a weekend and successfully replaced a Windows server farm with a 386 running Gentoo. We're a veritable community of geniuses.
Amen. I learned so much from working on small, underpowered systems. Having to think about where your CPU cycles and disk space are going forces you to pick up much more of a feel for how things really work. (e.g. I'm running out of space in/var - let's see what all those files are *really* for. What packages can I lose? What can I turn off or tweak? Is there a better way of doing this?)
Eventually you acquire a low-level "feel" for what the machine's doing, and that's how you're able to fix problems later along the line. I know it doesn't matter in the long run, but I *hate* seeing inefficient use of resources. Even things like scripts using awk when they could use cut piss me off. It's lazy. Understand your craft.
Over the last ten years my computers have got faster and faster. (Also hotter and hotter and louder and louder.) Have I got more and more productive? No. I can't write a letter any more quickly with Word on a 2+GHz XP machine than I could with Wordworth on my 30MHz Amiga in 1992.
I haven't replaced my personal machine in about five years, and I've got no plans to do so any time soon. Even 20GHz won't make me write quicker, read quicker or think quicker. I'm more interested in machines running cooler, quieter and cheaper.
I do./configure --prefix=/usr/local/pkg_name plus whatever other options, then make. When make finishes, I mkdir/usr/local/pkg_name-version, and ln -s/usr/local/pkg_name to that, then make install.
I get all my applications in their own directory, and it's only a matter of changing a link to roll back a version or two. It's also easy to copy an app to another host.
Some discretion is necessary here: I just dump a lot of small stuff into/usr/local (gnu utils like groff, less, stuff like that) only things like gimp, gcc, TeX, python etc get their own directory. This keeps the PATH sensible.
My main OS is Solaris, but I employ this technique on HP-UX, Linux, BSD, whatever I'm working on at the time. Keeps things simple for me, and it's easy to tell someone else just where things are.
The only time I go outside the app dir is for things like logs, which always live in/var/log/app_name, and tablespaces. I always try to keep/usr/local as static as possible.
As for maintining consistency across a network - NFS?
Slashdot Mirror
Why is everyone so keen to bash Enterprise? Seems even a lot of Trek fans just /want/ it to fail.
Okay, so a few episodes have sucked pretty bad, but all in all it's a pretty entertaining show. Decent actors, nice sets and effects, some good stories.
I'm a pretty keen Trek fan, and I don't really care about the inconsistencies with other series: I just what to be entertained for an hour, and Enterprise usually manages to do that.
Now, Voyager, on the other hand. THAT sucked total ass...
Episode II sucks way more than Episode I.
But then, as it's a prequel *and* a sequel, that was probably to be expected.
you just have to go back twice. On its way back to the future your first self runs over your recently arrived second self, the girl takes pity on you, looks after you, falls for you. Isn't that how it works?
Maybe I just watch too many movies...
You're all saying what a dork etc he is for getting so het up about this, or for quitting his job, but everyone seems to be overlooking the dorkiest fact of all: HE WAS PRESIDENT OF A LINUX USER GROUP.
He probably just got a girlfriend and has to drive her somewhere on Thursday nights.
> I've resigned from my subscription to Penthouse when I got married.
I quit mine when I got broadband.
I used to love the Amiga. I still have two (A1200 and A4000.) Sometimes I use them, primarily to run Bars and Pipes, and I'm always amazed at how speedy and pleasant they are to use. But, I let it go as a serious computing platform a long time ago.
Like most people here, I originally saw this release as pointless - who would use such a thing when they can use a Unix derivative or a Mac? What a silly OS, with no applications. Then I got round to thinking what I use my computers for.
I run Solaris on my desktop and Linux on my laptop, and all I do with them is web browsing, mail, a bit of coding (mostly web stuff), some graphics stuff, and then just general tinkering. I think the same goes for a lot of other people here.
If I could get a nice stable port of GCC, GIMP, Apache, PHP, an nice browser and a decent mail client, then I could very happily use an Amiga, and I'd have a whole new OS to play with. So why not?
Make a quiet, decent looking off-the-shelf machine running this OS, sell it for a fair price and I for one might be interested.
> There may be a more irrelevant and useless project in the world
There are about 79,000 of them on Sourceforge. (Conservative estimate.)
I'm splitting a mirror off my pr0n every night, just in case.
That's so true. Someone calls me in a public place, I retreat to somewhere where I won't annoy people, and if I can't do that, I speak quietly, and try to keep the length of the conversation to an absolute minimum. Usually I'll just say I'll call them back when it's more convenient for me.
Asshole has such an over-developed sense of self-importance that he thinks his conversation is not only more important than the peace of the people around him, but that the pathetic rabble will be impressed by his long, loud conversation. Or perhaps it's just that so many folk don't have any respect for the people around them.
The thing I really hate about modern phones is that so many have cameras. Take, for instance, the proliferation of twats in pubs and clubs pointing the phone at any half dressed/half attractive woman in sight, aiming up skirts and down tops for the leering benefit of equally twattish friends elsewhere.
> Everyone that hears it thinks it's really cool.
I call your bluff on that one.
I'm talking *very* long term. Working up to sending very large, or multiple, instruments. Things of roughly equivalent size to a person and what they would need to survive. (You could, of course, send multiple craft some unmanned carrying backup systems and supplies.)
I appreciate even that isn't the same, but it's a hell of a lot closer than we are now. You then just have to extend existing technology rather than creating it from scratch. I'm not talking about sending something the size of a TV set here.
If I may use your own analogy, we have a small sub with cameras. Next we build a bigger one with more powerful lights and better arms. Then another, probably bigger still, more powerful, capable of, say, drilling into the sea bed. Then another with a small automated laboratory on board. That might be the size of a car. You're already much closer to being able to build something that might carry a man. You're not there, but you're nearer, and you've done a lot of worthwhile science in the process.
I guess what I'm trying to say is that sending people is only justified when the cost is reasonable, and for the cost to be reasonable most of the technology to do the job must be in place.
Trying to send people now is like building your nuclear sub when we've just mastered the waterproof camera. Building a small manned sub when we're very good at building similar sized unmanned ones is not so unreasonable.
Send orbiters, probes, robots. Make them bigger and more sophisticated as you go along. Send things that take samples and come back. Do this often enough and eventually you reach the limits of what unmanned technology can accomplish, but by then the launching and recovery systems should be so proven and capable that sending a person becomes little more complicated than sending a couple of big packages of instrumentation.
Gradually work towards sending a person and bringing them back by sending lots of expendable things, and bringing them back with stuff for us to study here. Scale up as we go along instead of having one immediate big push. Isn't that sensible?
It's amazing how many people on here have single handedly saved companies, made stock rise 1000%, rewritten legacy applications in a weekend and successfully replaced a Windows server farm with a 386 running Gentoo. We're a veritable community of geniuses.
Amen. I learned so much from working on small, underpowered systems. Having to think about where your CPU cycles and disk space are going forces you to pick up much more of a feel for how things really work. (e.g. I'm running out of space in /var - let's see what all those files are *really* for. What packages can I lose? What can I turn off or tweak? Is there a better way of doing this?)
Eventually you acquire a low-level "feel" for what the machine's doing, and that's how you're able to fix problems later along the line. I know it doesn't matter in the long run, but I *hate* seeing inefficient use of resources. Even things like scripts using awk when they could use cut piss me off. It's lazy. Understand your craft.
Over the last ten years my computers have got faster and faster. (Also hotter and hotter and louder and louder.) Have I got more and more productive? No. I can't write a letter any more quickly with Word on a 2+GHz XP machine than I could with Wordworth on my 30MHz Amiga in 1992.
I haven't replaced my personal machine in about five years, and I've got no plans to do so any time soon. Even 20GHz won't make me write quicker, read quicker or think quicker. I'm more interested in machines running cooler, quieter and cheaper.
Nope. People are still finding new ways to levarage it.
Hey man, no need to loose your cool.
Yeah, why can't everyone just get along? M'kay?
I really don't get why you're all so rabid about this.
.tgz of the source code, under the GPL. What exactly do you all plan to do with it?
Say tomorrow morning ftp.sun.com has a big old
Why do so many linux users take it as a personal insult when someone refuses to give them something for free? (Code, music, movies, whatever.)
Tell me that!
> april fools jokes are funny when they are reasonably real
They're funny when you're nine. Possibly.
However many jobs I have, "this one" is always the worst one.
> But General Motors doesn't want to see that in the U.S...
I heard some guy made a water powered car, and they suppressed that too. Or maybe that was somebody else. But whatever. THE POINT STANDS.
I do ./configure --prefix=/usr/local/pkg_name plus whatever other options, then make. When make finishes, I mkdir/usr/local/pkg_name-version, and ln -s /usr/local/pkg_name to that, then make install.
/usr/local (gnu utils like groff, less, stuff like that) only things like gimp, gcc, TeX, python etc get their own directory. This keeps the PATH sensible.
/var/log/app_name, and tablespaces. I always try to keep /usr/local as static as possible.
I get all my applications in their own directory, and it's only a matter of changing a link to roll back a version or two. It's also easy to copy an app to another host.
Some discretion is necessary here: I just dump a lot of small stuff into
My main OS is Solaris, but I employ this technique on HP-UX, Linux, BSD, whatever I'm working on at the time. Keeps things simple for me, and it's easy to tell someone else just where things are.
The only time I go outside the app dir is for things like logs, which always live in
As for maintining consistency across a network - NFS?
shouldn't they write some documentation first?
Chalk one up for Sun. Serial access since year dot.