...the Marines are the front-line troops. Every Marine is a warfighter. There are no Marine mechanics or Marine medtechs.
If we were in a situation where nonlethals are called for, we won't need the Marines. If the Marines have been called in, we're far past nonlethals.
This whole thread is something of a non sequitur.
And they're asking the old signups for input
on
VeriSign Usurps .com
·
· Score: 2
Um. This is a proposal. Nothing's been signed yet.
Not only that...
I was one of those who signed up for the Members At Large thingy, back before I realized that it was a bread-and-circuses appeasement move that had fuck-all to do with the actual outcome. And today in my email was a message from ICANN to all the signups saying that input was being solicited via an opt-in mailing list.
My sincere willingness to help is waging a pitched battle with my pragmatism and realism and pessimism and inherent cynicism right now. Hmmmm...
So ironic... I ask people to behave fairly, and it's a high moral ground. Somebody out there raises the article by *one* point, and it's karma whoring. Oh well, gotta get the minimum flame quotas in for the day, I guess.
I never said it wasn't a funny picture. I was one of the first to send it around.:-) It was even better since I had just flown a long trip when the picture was taken and released, but that's another story.
Also -- as anyone with experience diagnosing any kind of hardware problems can tell you -- simply because <random flavor of Unix> says that you have a hardware problem does not necessarily mean that it's true. When it comes to hardware problems, Unix ain't all that much better at self-diagnosis.
For software problems, of course, Unix kicks ass.:-)
...and we should stop using it as evidence of Linux/*BSD stability.
Look close enough and you'll see that the fault number is the one meaning "hardware failure," specifically bad RAM. I don't believe that Linux performs any better when the RAM suddenly craps out.
I like the 8-bit version of Cox-on-a-chip though.:-)
> look
You are trapped in a twisty maze of symlinks, all alike. You are likely to be eaten by init.
Well, at least it's successful for Linux...
on
KDE 2.1 Is Out
·
· Score: 2
I'd love to be able to demonstrate how wonderful KDE and OSS projects are to my disbelieving coworkers...
Unfortunately, I can't. We all use Solaris here, and the last version of KDE that even pretended to run under Solaris was 2.0. And it does a damn poor job at that. KDE 2.0.1 looks beautiful on my Linux desktop, but we can't do that for production servers.
So all I can do is say, lamely, "Well, it works really really well... on one platform..." And that makes my disbelieving coworkers... correct.
Re:My other comment is wacked! I was in a hurry
on
Mission of Gravity
·
· Score: 2
Yes, and the pub was nicknamed the Bird and Baby by the Inklings and others in the Oxford area.:-) Believe me, I follow Tolkien quite closely.
Christopher Tolkien did eventually publish what his father had written as far as the "time travel" story went. I *think* it's entitled _The Lost Road_, although I may be remembering some other Tolkien work. It's not time travel in the sense that we tend to think of it now -- there's no sudden *pop* and suddenly they're in the Second Age chatting with Celebrimbor and they have to careful not to reveal the future while being chased by Sauronic Daleks yadda yadda yadda.:-)
If you haven't already, do pick up the published Letters of JRR Tolkien. Really fascinating work.
I do suggest you look into the C.S. Lewis Space trilogy if you haven't.
Oh, it's definitely on my list. As you probably know, Lewis and J.R.R. Tolkien challenged one another; Lewis wrote on space travel and eventually churned out a whole trilogy. Tolkien wrote on time travel but never published the result himself.
Another classic -- Dragon's Egg by Robert Forward
on
Mission of Gravity
·
· Score: 3
Large parts of the plot take place on the surface of a neutron star. Yeah, that's right, a neutron star. Forward's a physicist.
Makes some really interesting ideas as far as what life would be like when walking against a magnetic field is almost impossible. And for the younger trolls of/. there's even a alien threesome sex scene. (I don't know why. It has nothing to do with the plot.)
Sorry about the typos; someone turned up the building chillers and my fingers are about frozen.
Calling the DES replacement AES is like naming a specific product "new" or "ultimate". Five years later it isn't new, and what are you going to call its replacement? "really ultimate, we mean it this time"?
Calling DES by its name now feels silly because the S is more or less false. Three decades from now we'll feel silly calling these algorithms AES, because our hardware will be able to crack 128-bit keys in eight seconds (while ripping mp3's, of course), and that hardly counts as "Advanced".
Still, I'm looking forward to Razjdxndawl. (I can pronounce it no problem, but heck if I can remember how to spell it.)
So, the series I would make is about a covert team
that goes from planet to planet, helping smooth the way as each planet makes the final leap and joins the Federation.
Because they are covert they can't just run around with phasers, communicators, and other gadgets, and they can't
just beam out whenever they feel like it.
I once got suckered into reading a ST novel. I don't recall the author, but the title was "Prime Directive". Basically, there's a whole bunch of the covert monitoring stuff surrounding a culture that's almost ready to join, yadda yadda, then Kirk manages to cause total nuclear devastation of the entire planet, which counts as "interference in the natural development of the people," go figure, and has to stand trial for it, yadda yadda, until Spock bails his ass out again.
I don't know whether you could make an entire series out of this. Even this novel started off with some interesting scenes, but was hard put to come up with a good ending. (Actually, it failed miserably to come up with a good ending. Oh look, a universe-eating monster in the last five pages.)
I do agree with you on this, however: reducing the level of tech available would make the show watchable again. (I nearly vomit when a character asks the computer to speculate on something, and it does so with complete accuracy in less than a second. If the characters could really do that... they wouldn't need to.
I too was amazed that Mr. Breathed consented to the interview. Just goes to show what an amazingly froody guy he is. (Zero points for catching the reference.)
And the first half of the interview was well presented...
And then we're taken to the second website, which is so loaded with graphics and tables that after three minutes I'm slapping the Esc key begging it to stop loading so I can get the hell out. Eventually it rendered something, with the text of the interview in a two-inch column running down the side of the browser window. Plus a retelling of the same "how we cold-called Breathed and lived to tell about it" that we got in the first half, with the addition of crappy style.
Ah well. Just had to rant. I can't stand online magazines.
...as a student assistant sysop were most excellent.
While the money wasn't the absolute greatest, the employers had no problems whatsoever working around my class schedule. Go figure -- my class schedule was the reason I was there!
At 3:00 AM when we're all there working on the assignment, and somebody does Something Bad to the central server, it was very helpful to put on the "job" hat, fix it, and then go back to being a student.
You'd better fscking believe that my code was portable. Every idea we (student assistants) came up with had to work on over a half dozen flavors of Unix, most of which nobody's ever heard of today. Many of the systems weren't "public" machines; they just were there to run small networks. So no cool utilities which happen to hog diskspace or require boatloads of RAM. That meant we had to learn the core common Unix tools well.
We weren't allowed to run riot on the heavily-used systems. Basically, any systems on which professors might store data (e.g., final exams), we were by default not given the root password.
All of this has been to my benefit now that I'm working full-time. Good experience, good training. Even the professors liked it.
(I wonder if I'll be able to post this, given that/. seems determined to forget who I am...)
Organisation Name.... Rainforest Consulting
Organisation Address. 2180 Pleasant Hill Road, Suite A-5, #376
Organisation Address.
Organisation Address. Duluth
Organisation Address. 30096
Organisation Address. GA
Organisation Address. UNITED STATES
Yes, rpm is a pain in the ass. I much prefer the packaging software that's been around a lot longer, like that under Solaris or Digital Unix or IRIX.
And, by the way, if symbol versioning is good, why is it even an option to build without it?
Because it isn't easily automated. You must choose which symbols get exported, which get restricted, and what version number goes with each symbol. Some symbols (which ones?) might get their versions incremented (by how much?) for a particular build, and some won't, depending on you and your app.
...but nobody reads the documentation anymore, so they bring problems on themselves.
1.17. What is symbol versioning good for? Do I need it?
{AJ} Symbol versioning solves problems that are related to interface
changes. One version of an interface might have been introduced in a
previous version of the GNU C library but the interface or the semantics of
the function has been changed in the meantime. For binary compatibility
with the old library, a newer library needs to still have the old interface
for old programs. On the other hand, new programs should use the new
interface. Symbol versioning is the solution for this problem. The GNU
libc version 2.1 uses symbol versioning by default if the installed binutils
supports it.
We don't advise building without symbol versioning, since you lose binary
compatibility - forever! The binary compatibility you lose is not only
against the previous version of the GNU libc (version 2.0) but also against
all future versions.
Using private interfaces, using static libraries, not using versioning even when shared libraries are in use... I'm not surprised Oracle had problems.
Despite myriad Internet reports to the contrary, the "new"
ST:TMP will not feature a great deal of previously unseen
footage (including the infamous "memory wall"
Kirk-Spock spacewalk sequence that takes place inside
V'ger).
Huh?
Okay, I am not a Star Trek fan. At all. But I recognize most of the references that you often hear these days. What's this one?
I usually never even see AC posts, but fortunately for you I fscked up my browsing settings. (They're fixed now, BTW.) No, I don't have a link, but it's been tossed around on the mailing lists several times. You can go to http://gcc.gnu.org/ and search the lists. I don't think it ever got formalized to one of the extensions listed on the Extensions page.
I've been looking at Doxygen to help document the guts of the new replacement libstdc++-v3 library. These scripts would also help, in a big way.
I very much want to run the code for the compiler itself through these scripts and doxygen.
Many people, over the last year-and-some-odd, have made good progress towards implementing a new back-end target in GCC: an XML generator for your code. Rather than creating assembly, GCC would create XML. (And you'd better damn well believe that the first thing we'd run through it would be the sources to the compiler itself!:-)
I completely fail to grok the attraction of televised sport. Except for women's beach volleyball, which is always, um,
bouncy.
I think that's the main attraction of the XFL: the cheerleaders. It's also the major application of technology in the game; whole new breakthroughs in silicone and saline...
...following yours is trolling, "Why do gay people always have to advertise that they're gay?"
Me, I had no idea either that Allman is gay. I guess he's the kind of professional that feels we should all be concentrating on what kind of code the other person writes rather than the gender that other person is dating.
Einstein said that you should never memorize what you can look up.
Remember Sean Connery as Indiana Jones' father in the most recent movie? Indiana asks him something, Dad says it's in his diary and he doesn't know, Indiana disbelievingly asks him if he can't remember, Dad summons up his dignity and replies, "I wrote it down so that I wouldn't have to remember."
Or my favorite quote from Alan Turing (paraphrased): Programming should always be exciting, because as soon as something becomes boring or repetitive, it should be turned over to the machine.
I've automated so many of my sysadmin duties that I can't remember how to do them manually anymore.:-) Frees up more time for programming.
Slashdot Mirror
...as in, I say there old chap, bloody Microsoft seems to have gone and buggered my web page again.
...the Marines are the front-line troops. Every Marine is a warfighter. There are no Marine mechanics or Marine medtechs.
If we were in a situation where nonlethals are called for, we won't need the Marines. If the Marines have been called in, we're far past nonlethals.
This whole thread is something of a non sequitur.
Not only that...
I was one of those who signed up for the Members At Large thingy, back before I realized that it was a bread-and-circuses appeasement move that had fuck-all to do with the actual outcome. And today in my email was a message from ICANN to all the signups saying that input was being solicited via an opt-in mailing list.
My sincere willingness to help is waging a pitched battle with my pragmatism and realism and pessimism and inherent cynicism right now. Hmmmm...
So ironic... I ask people to behave fairly, and it's a high moral ground. Somebody out there raises the article by *one* point, and it's karma whoring. Oh well, gotta get the minimum flame quotas in for the day, I guess.
I never said it wasn't a funny picture. I was one of the first to send it around. :-) It was even better since I had just flown a long trip when the picture was taken and released, but that's another story.
Also -- as anyone with experience diagnosing any kind of hardware problems can tell you -- simply because <random flavor of Unix> says that you have a hardware problem does not necessarily mean that it's true. When it comes to hardware problems, Unix ain't all that much better at self-diagnosis.
For software problems, of course, Unix kicks ass. :-)
...and we should stop using it as evidence of Linux/*BSD stability.
Look close enough and you'll see that the fault number is the one meaning "hardware failure," specifically bad RAM. I don't believe that Linux performs any better when the RAM suddenly craps out.
I like the 8-bit version of Cox-on-a-chip though. :-)
> enter
> look
You are trapped in a twisty maze of symlinks, all alike. You are likely to be eaten by init.
I'd love to be able to demonstrate how wonderful KDE and OSS projects are to my disbelieving coworkers...
Unfortunately, I can't. We all use Solaris here, and the last version of KDE that even pretended to run under Solaris was 2.0. And it does a damn poor job at that. KDE 2.0.1 looks beautiful on my Linux desktop, but we can't do that for production servers.
So all I can do is say, lamely, "Well, it works really really well... on one platform..." And that makes my disbelieving coworkers... correct.
Yes, and the pub was nicknamed the Bird and Baby by the Inklings and others in the Oxford area. :-) Believe me, I follow Tolkien quite closely.
Christopher Tolkien did eventually publish what his father had written as far as the "time travel" story went. I *think* it's entitled _The Lost Road_, although I may be remembering some other Tolkien work. It's not time travel in the sense that we tend to think of it now -- there's no sudden *pop* and suddenly they're in the Second Age chatting with Celebrimbor and they have to careful not to reveal the future while being chased by Sauronic Daleks yadda yadda yadda. :-)
If you haven't already, do pick up the published Letters of JRR Tolkien. Really fascinating work.
I do suggest you look into the C.S. Lewis Space trilogy if you haven't.
Oh, it's definitely on my list. As you probably know, Lewis and J.R.R. Tolkien challenged one another; Lewis wrote on space travel and eventually churned out a whole trilogy. Tolkien wrote on time travel but never published the result himself.
Large parts of the plot take place on the surface of a neutron star. Yeah, that's right, a neutron star. Forward's a physicist.
Makes some really interesting ideas as far as what life would be like when walking against a magnetic field is almost impossible. And for the younger trolls of /. there's even a alien threesome sex scene. (I don't know why. It has nothing to do with the plot.)
Sorry about the typos; someone turned up the building chillers and my fingers are about frozen.
Calling the DES replacement AES is like naming a specific product "new" or "ultimate". Five years later it isn't new, and what are you going to call its replacement? "really ultimate, we mean it this time"?
Calling DES by its name now feels silly because the S is more or less false. Three decades from now we'll feel silly calling these algorithms AES, because our hardware will be able to crack 128-bit keys in eight seconds (while ripping mp3's, of course), and that hardly counts as "Advanced".
Still, I'm looking forward to Razjdxndawl. (I can pronounce it no problem, but heck if I can remember how to spell it.)
I once got suckered into reading a ST novel. I don't recall the author, but the title was "Prime Directive". Basically, there's a whole bunch of the covert monitoring stuff surrounding a culture that's almost ready to join, yadda yadda, then Kirk manages to cause total nuclear devastation of the entire planet, which counts as "interference in the natural development of the people," go figure, and has to stand trial for it, yadda yadda, until Spock bails his ass out again.
I don't know whether you could make an entire series out of this. Even this novel started off with some interesting scenes, but was hard put to come up with a good ending. (Actually, it failed miserably to come up with a good ending. Oh look, a universe-eating monster in the last five pages.)
I do agree with you on this, however: reducing the level of tech available would make the show watchable again. (I nearly vomit when a character asks the computer to speculate on something, and it does so with complete accuracy in less than a second. If the characters could really do that... they wouldn't need to.
Yeah, but you recognized it. :-)
I too was amazed that Mr. Breathed consented to the interview. Just goes to show what an amazingly froody guy he is. (Zero points for catching the reference.)
And the first half of the interview was well presented...
And then we're taken to the second website, which is so loaded with graphics and tables that after three minutes I'm slapping the Esc key begging it to stop loading so I can get the hell out. Eventually it rendered something, with the text of the interview in a two-inch column running down the side of the browser window. Plus a retelling of the same "how we cold-called Breathed and lived to tell about it" that we got in the first half, with the addition of crappy style.
Ah well. Just had to rant. I can't stand online magazines.
...as a student assistant sysop were most excellent.
All of this has been to my benefit now that I'm working full-time. Good experience, good training. Even the professors liked it.
(I wonder if I'll be able to post this, given that /. seems determined to forget who I am...)
Yet.
Yes, rpm is a pain in the ass. I much prefer the packaging software that's been around a lot longer, like that under Solaris or Digital Unix or IRIX.
And, by the way, if symbol versioning is good, why is it even an option to build without it?
Because it isn't easily automated. You must choose which symbols get exported, which get restricted, and what version number goes with each symbol. Some symbols (which ones?) might get their versions incremented (by how much?) for a particular build, and some won't, depending on you and your app.
...but nobody reads the documentation anymore, so they bring problems on themselves.
Using private interfaces, using static libraries, not using versioning even when shared libraries are in use... I'm not surprised Oracle had problems.
Huh?
Okay, I am not a Star Trek fan. At all. But I recognize most of the references that you often hear these days. What's this one?
...the open source game Xconq. That one really huge map of the world is way, way impressive.
("Way impressive" is a technical term they learnt me in college...)
I usually never even see AC posts, but fortunately for you I fscked up my browsing settings. (They're fixed now, BTW.) No, I don't have a link, but it's been tossed around on the mailing lists several times. You can go to http://gcc.gnu.org/ and search the lists. I don't think it ever got formalized to one of the extensions listed on the Extensions page.
I've been looking at Doxygen to help document the guts of the new replacement libstdc++-v3 library. These scripts would also help, in a big way.
I very much want to run the code for the compiler itself through these scripts and doxygen.
Many people, over the last year-and-some-odd, have made good progress towards implementing a new back-end target in GCC: an XML generator for your code. Rather than creating assembly, GCC would create XML. (And you'd better damn well believe that the first thing we'd run through it would be the sources to the compiler itself! :-)
I think that's the main attraction of the XFL: the cheerleaders. It's also the major application of technology in the game; whole new breakthroughs in silicone and saline...
...following yours is trolling, "Why do gay people always have to advertise that they're gay?"
Me, I had no idea either that Allman is gay. I guess he's the kind of professional that feels we should all be concentrating on what kind of code the other person writes rather than the gender that other person is dating.
Remember Sean Connery as Indiana Jones' father in the most recent movie? Indiana asks him something, Dad says it's in his diary and he doesn't know, Indiana disbelievingly asks him if he can't remember, Dad summons up his dignity and replies, "I wrote it down so that I wouldn't have to remember."
Or my favorite quote from Alan Turing (paraphrased): Programming should always be exciting, because as soon as something becomes boring or repetitive, it should be turned over to the machine.
I've automated so many of my sysadmin duties that I can't remember how to do them manually anymore. :-) Frees up more time for programming.