NO. It's NOT a joke. It's REALLY gonna happen. And it's not going to take just a day. It'll take a whole frickin' decade. So, just shut down your machine for the next machine, or the badass uberbots will fry yo' ass!
BTW, if any Apple people are reading this, go to the GNUstep website. They're moving right along on the OpenStep spec, including the new routines introduced by MacOS X.:^)
Do you count, say, numbers from the Linux Counter Project? (or whatever the hell it's called?) That can be easily spoofed. Do you count sales of Linux distros? Very misleading. Number of sales AND downloads? Misleading as well. Servers running on the 'Net? Misleading, especially considering the fact that some of those machines that report one thing are, in fact, another (I know folks who have set up Linux boxen to look like WinNT & MacOS to the outside world...now, I'm not just talking about Samba and NetaTalk, I'm talking other ways too that non-gurus like myself just smile, nod, and say "what's the fuckin' point" to.
Einstein was a genius, not God, and came up with theories of relativity. NOT FACTS.
Theories are NOT facts until proven so in rigorous experimentation. He was brilliant-but not perfect, and it may be a long time before we prove just how brilliant, or perfect, he was. Please don't discount others' theories just because they don't go along with Einstein's theories. He didn't invent or create the rules of the universe--just theorized about them.
I take this back if you can prove Einstein's Godlike powers.:^)
Heck, if you want to get down to it, in a way Star Trek has even insulted the tech crowd with the Borg-gee, a technologically advanced race, who obviously has taken prostetics and networking to its "logical" end. Please.
Uhhh...I hate to point it out, but it'd be difficult (at best) to get binary compatibility on an x86 version of OS X...it's kind of like (pardon the pun) mixing apples and oranges.
Okay, not only that, but he builds his *own* analog equipment. And he writes his own sequencer stuff. Show me an analog sequencer, and I'll cream my jeans again.:^)
It's *not* a pile of horse manure. Not only does he use Macs, but he's even built his own samplers. Show me an analog additive-synthesis sampler, and I'll cream my jeans.:^)
OTOH, if your fictional character of Ham Sandwich were to be an interstellar ham smuggler, you'd be OK, at least in the US, because that could be considered to be parody (although IANAL.):^)
I suppose Samuel Clemens isn't literature, either.
*sighs* guess I'll have to throw away my collection...they seem so happy on the bookshelf, though...and yes, there are a large number of O'Reilly books there, too.:^)
Actually, if something doesn't respond to killing nicely, I doubt if a script is much more efficient than I would be on my own.
My personal feeling is that daemons *should* be written in such a way that one can simply kill them. Simply writing a script to get around this is just a sloppy hack to fix a problem.
A lot of newer distros, including the one I use, tend to use the Windows "magic hardware" approach: if the hardware works, we have good magic; if it doesn't work, there's some bad magic at work, and we shake our heads and fire off emails saying "my sound card don't work.":^)
Quite frankly, this can be a bit annoying. A prime example is my personal system. I just did a clean install of Linux-Mandrake 7.0. I have a Voodoo3 2000. I received no messages regarding what card I had (strange) what kind of mouse I had (I know what it is, but this is also strange), but, despite the lack of messages, gee, it just kinda magically worked.
Problem: Linux-Mandrake 7.0 installs some X server I've never heard of: XF86_3dfx. If you get the RPMs (boo, hiss) off of linux.3dfx.com, this is essentially the SVGA X server with V3/Banshee support. On top of that, the XF86_3dfx server doesn't support the Microsoft IntelliMouse (strange; the darn things are so common now on newer machines.) I didn't get to test 3D libs on it, because I replaced the X server too quickly.:^) (NOTE: The regular 3dfx X server needs to be running in order for Glide to work. Again, boo, hiss.)
Quite frankly, I was a bit of an idiot about hardware when I installed Slackware. I stuck with it out of a genuine desire for a more stable, more configurable operating system. If all these folks need a brain-dead installer and no fussing with hardware settings, then I suggest these folks invest in Apple hardware. I believe that, thanks to their monopoly on the Mac market, that hardware support is a relatively low issue.
The real problem is that, IMHO, Red Hat, etc. are just not as intuitive.
Once one learns how to write some fairly simple shell scripts, one can work on a Slackware system's init scripts (I was within a couple of weeks after starting to use Linux.)
I've been running SysV-based systems for a coupla years now, and I'm still a teensy bewildered by the logic behind the scripts. Ugh. I tend to add/remove "services" through my rc.local, about the same as I did on my Slackware machine.
As far as starting/stopping "services," I usually look for the process running the service, and issue a kill -9 or simply kill. This tends to kill a service dead, in most cases, unless it has the ability to respawn on its own (handy at times, usually just annoys me.)
Actually this is subjective. Having cut my milk teeth on Unix inside of AT&T, I find the Sys V init scripts more intuitive. It's the whole nature vs. nurture thing.
Hmmm...I bet that's why the original comment included IMO.
I agree with you. I find RPM to be a real pain...I'd like to lobotomize the poor Linux-Mandrake system I'm using now. Real nice, real slick...but, Gawd, if you install something from source!:^)
I remember in my college days a diehard Slackware guy that ran a local LUG really touted RPM, based on the fact that the packages could be signed. Well, whoopty-frickin-doo. I trust that as far as ActiveX certificates. Anyone remember the Internet Exploder control fiasco when ActiveX first came out? If you don't, it was an ActiveX control, certified by Microsoft (later quickly pulled) that essentially shut down a Win95 machine. The point: things like PGP signatures and certificates are merely fluff.
As far as dependencies go, I've seen dependencies that I KNEW were only half-right, yet I either had to upgrade packages or had to simply force the install simply because the package maintainer had a (slightly) newer version of a lib or app.
Once you take away digital sigs and package deps, all RPMs are are CPIO archives with extra crap. Nothing more.
Hey, ya gotta love the Star Trek transporter system, if for no other reason that they get around the Heisenberg Uncertainty Principle by, voila, using a Heisenberg Compensator
HINT: The Heisenberg Uncertainty Principle, as I understand it though IANAP, states that one cannot know where more than one particle (is this right?) is at any given moment. Magic, I say. I bet having a job on the writing staff at Paramount would be fun as shit.:^)
Slashdot Mirror
FUCK! SHIT! BALLS!! FUCK!!! SHIT!!!
###### ######### ######### #
#
NO. It's NOT a joke. It's REALLY gonna happen. And it's not going to take just a day. It'll take a whole frickin' decade. So, just shut down your machine for the next machine, or the badass uberbots will fry yo' ass!
Fuck! Shit! FUCK!!!
BTW, if any Apple people are reading this, go to the GNUstep website. They're moving right along on the OpenStep spec, including the new routines introduced by MacOS X. :^)
Well, that would be difficult.
Do you count, say, numbers from the Linux Counter Project? (or whatever the hell it's called?) That can be easily spoofed. Do you count sales of Linux distros? Very misleading. Number of sales AND downloads? Misleading as well. Servers running on the 'Net? Misleading, especially considering the fact that some of those machines that report one thing are, in fact, another (I know folks who have set up Linux boxen to look like WinNT & MacOS to the outside world...now, I'm not just talking about Samba and NetaTalk, I'm talking other ways too that non-gurus like myself just smile, nod, and say "what's the fuckin' point" to.
Einstein was a genius, not God, and came up with theories of relativity. NOT FACTS.
Theories are NOT facts until proven so in rigorous experimentation. He was brilliant-but not perfect, and it may be a long time before we prove just how brilliant, or perfect, he was. Please don't discount others' theories just because they don't go along with Einstein's theories. He didn't invent or create the rules of the universe--just theorized about them.
I take this back if you can prove Einstein's Godlike powers. :^)
I have to say I feel the same...
Heck, if you want to get down to it, in a way Star Trek has even insulted the tech crowd with the Borg-gee, a technologically advanced race, who obviously has taken prostetics and networking to its "logical" end. Please.
Uhhh...I hate to point it out, but it'd be difficult (at best) to get binary compatibility on an x86 version of OS X...it's kind of like (pardon the pun) mixing apples and oranges.
Sorry to feed the troll, but I have to state the obvious:
Darwin is a BSD variant. More than likely, it will be released under the BSD license (duh.)
True, and remember that MMX was first...
You left a sentence fragment there...or did you mean too?
Okay, not only that, but he builds his *own* analog equipment. And he writes his own sequencer stuff. Show me an analog sequencer, and I'll cream my jeans again. :^)
It's *not* a pile of horse manure. Not only does he use Macs, but he's even built his own samplers. Show me an analog additive-synthesis sampler, and I'll cream my jeans. :^)
OTOH, if your fictional character of Ham Sandwich were to be an interstellar ham smuggler, you'd be OK, at least in the US, because that could be considered to be parody (although IANAL.) :^)
I suppose Samuel Clemens isn't literature, either.
:^)
*sighs* guess I'll have to throw away my collection...they seem so happy on the bookshelf, though...and yes, there are a large number of O'Reilly books there, too.
We like these kinds of stories because, hey, it's cool. :^) Who cares if it's practical or not.
:^)
Lighten up, willya?
Actually, if something doesn't respond to killing nicely, I doubt if a script is much more efficient than I would be on my own.
My personal feeling is that daemons *should* be written in such a way that one can simply kill them. Simply writing a script to get around this is just a sloppy hack to fix a problem.
A lot of newer distros, including the one I use, tend to use the Windows "magic hardware" approach: if the hardware works, we have good magic; if it doesn't work, there's some bad magic at work, and we shake our heads and fire off emails saying "my sound card don't work." :^)
:^) (NOTE: The regular 3dfx X server needs to be running in order for Glide to work. Again, boo, hiss.)
Quite frankly, this can be a bit annoying. A prime example is my personal system. I just did a clean install of Linux-Mandrake 7.0. I have a Voodoo3 2000. I received no messages regarding what card I had (strange) what kind of mouse I had (I know what it is, but this is also strange), but, despite the lack of messages, gee, it just kinda magically worked.
Problem: Linux-Mandrake 7.0 installs some X server I've never heard of: XF86_3dfx. If you get the RPMs (boo, hiss) off of linux.3dfx.com, this is essentially the SVGA X server with V3/Banshee support. On top of that, the XF86_3dfx server doesn't support the Microsoft IntelliMouse (strange; the darn things are so common now on newer machines.) I didn't get to test 3D libs on it, because I replaced the X server too quickly.
Quite frankly, I was a bit of an idiot about hardware when I installed Slackware. I stuck with it out of a genuine desire for a more stable, more configurable operating system. If all these folks need a brain-dead installer and no fussing with hardware settings, then I suggest these folks invest in Apple hardware. I believe that, thanks to their monopoly on the Mac market, that hardware support is a relatively low issue.
The real problem is that, IMHO, Red Hat, etc. are just not as intuitive.
Once one learns how to write some fairly simple shell scripts, one can work on a Slackware system's init scripts (I was within a couple of weeks after starting to use Linux.)
I've been running SysV-based systems for a coupla years now, and I'm still a teensy bewildered by the logic behind the scripts. Ugh. I tend to add/remove "services" through my rc.local, about the same as I did on my Slackware machine.
As far as starting/stopping "services," I usually look for the process running the service, and issue a kill -9 or simply kill. This tends to kill a service dead, in most cases, unless it has the ability to respawn on its own (handy at times, usually just annoys me.)
Just my $0.02
Actually this is subjective. Having cut my milk teeth on Unix inside of AT&T, I find the Sys V init scripts more intuitive. It's the
whole nature vs. nurture thing.
Hmmm...I bet that's why the original comment included IMO.
I agree with you. I find RPM to be a real pain...I'd like to lobotomize the poor Linux-Mandrake system I'm using now. Real nice, real slick...but, Gawd, if you install something from source! :^)
I remember in my college days a diehard Slackware guy that ran a local LUG really touted RPM, based on the fact that the packages could be signed. Well, whoopty-frickin-doo. I trust that as far as ActiveX certificates. Anyone remember the Internet Exploder control fiasco when ActiveX first came out? If you don't, it was an ActiveX control, certified by Microsoft (later quickly pulled) that essentially shut down a Win95 machine. The point: things like PGP signatures and certificates are merely fluff.
As far as dependencies go, I've seen dependencies that I KNEW were only half-right, yet I either had to upgrade packages or had to simply force the install simply because the package maintainer had a (slightly) newer version of a lib or app.
Once you take away digital sigs and package deps, all RPMs are are CPIO archives with extra crap. Nothing more.
Uh...I think he meant control==oldschool :^)
Bicentennial Man
Hey, ya gotta love the Star Trek transporter system, if for no other reason that they get around the Heisenberg Uncertainty Principle by, voila, using a Heisenberg Compensator
:^)
HINT: The Heisenberg Uncertainty Principle, as I understand it though IANAP, states that one cannot know where more than one particle (is this right?) is at any given moment. Magic, I say. I bet having a job on the writing staff at Paramount would be fun as shit.
Well, damn, I guess the guy who put the page together was a real idiot for running FreeAmp then.