But what NineNine "expects" is unreasonable. I think the combination of paid support/access with ability to see and modify the source for a POS system is great! But no one should be expected to develop such a monstrosity just to do it, especially when there's no reasonable way the developer can test or deploy it!
I mean, do you have POS cash registers in your basement just waiting to be endowed with such an application? Come on.
I mean seriously. It bundles in plausible deniability into the network protocol. Stuff that into your pipe and smoke it.
If you want to do skunkworks-style development, collaboration, or your just an 'ARRRRR net pirate then WASTE is a tasty morsel of goodness that is hard to find in other products.
Point of sale system, right. You don't do that open source because there's no point. Who'd use it that doesn't have a purchasing department and thus can be expected to outlay a little dough?
As of late any time someone wants to look "smart" or "insightful" they post a link to linuxsecurity.org in response to a inane comment about Windows security. You take a site which wants to be honest about security issues in free OSs and use it as some kind of childish comeback.
Real good sleuthing there, Sherlock.
The only thing you've done is start a pissing contest. Just don't reply to posts that don't need replying to. The parent wasn't making an argument, but a joke. You should know that we bash Microsoft here, whether they deserve it or not, AND EVERYBODY KNOWS THAT. It's not like they need to be actively defended.
What's interesting about the 3 bugs, DIPSHIT, is that they were discovered by eEye (and others) some time back in late 2003 and they sat on their hands waiting for Microsoft to publically acknowledge them and release patches.
Meanwhile all of the listings on that front page are fresh and current, and advise you to disable services there aren't already patches for. So sit and spin, my friend.
the compression is software-based, so they can claim any compressed number they want, depending on what they are compressing. It has nothing to do with the medium.
I've always bought ZIP 250 (IDE, not SCSI) and have never had a problem. I've heard people bitch about the 100s but the price difference was never more than $15 and I never regretted that. Of course, now I just use USB keys. ^_-
Clearly some distribution with a moderate following has to stand up and say: "We will cater to the desktop realm" and they want capital to bring in HCI brains and work on bringing that stuff into line. And I'm not just talking abotu Helix or Lindows or Lycrosis here.
I mean Helix is Novell/Suse and they apparently don't have the cash for that now. Lindows is in it for the money, not advancing the state of the art.
I think you should just specify the platform. They (being those "other guys") only in it together against Intel x86. But if you want to argue platform features you have to be more specific than RISC (or "not x86") because they are not all created equal.
Specifically Intel's own new baby (Itanium2) probably has them panting and wheezing, with Power close behind. So... I don't know.
And all of them run Java slowly.;-D
I have a scary notion that a port of Mono would be end up working better on Unix/XYZ compared to Wintel.
GDM, Xauth and XFree do that because they like gethostbyname to figure out what to do. Best solution to prevent any rough spots during a network reconfigure is to just add the hostname(s) to the loopback interface line in your hosts file, which circumvents any IP addy / hostname / DNS issues.
The scripts have gotten a lot better since the pre-8.0 days. A lot of what was once shell scripts is now written in python with better error handling and re-use of common components. Not perfect, but some things, even the existing shell scripts (/etc/sysconfig/network/ifup-xxx for example) are downright pleasant to hook into and abuse.
Now, in my experience what people call RPM hell has always been a PEBCAK (no offense). RPMs are trackable and verifiable, more recently allow transactions and rollbacks, and lots of other goodies that few people want to learn how to use. Whenever you get stuck (often by a package maintainer's mistake in dependancies), the solution is almost always to build a needed RPM from source, but editing the spec file to remove the dependancies that conflict (but you KNOW are satisfied). If you know what you want, but can't get it to work, then you can force it without breaking consistency checks and carrying that shit forward. And uninstalling packages is not a bad thing (it doesn't clobber configuration files). You can back out of conflicting ones and repackage them into RPMs, this way you don't have to download them again later.
I mean really, the one-service-per-machine thing is a crock. You're telling me you can't simultaneously use postfix and apache on a machine installed from RPMs at once succesfully? What combinations of services have you found that don't mix? Come on, give me a break with the hyperbole.
The thing about Solaris is that they've got a much smaller target they need to worry about (limited hardware to support [no LAPTOPS], no catering to content creation/gamers, etc.). So of course they can make a very firm foundation... it's setup from the get-go to handle every type of machine it can be installed on and most every workload out of the box. You have to go out of your way to render the machine "barebones".
That being said, I like them. I like RedHat boxes too (just a little bit more, but not much). Hell, and SuSE is dandy too. Gosh darn it, I can even tolerate a Windows 2003 box.
apt for rpm is NO DIFFERENT than apt tooled for pkg. Moreover, with apt on RPM based systems I have a choice of (well last time I modifed sources.list) 8 different repositories for my package sources (source + binary) with various different political bents and countries of origin, so I get EVERYTHING.::glee!!!::
You've obviously never used RedHat long enough to appreciate it. You get used to the layout of/etc/sysconfig and the like. Also the installer and hardware detection is _tight_. (cliche, but 100% true). The only thing that still rubs me the wrong way is trying to patch kernel source RPMs, but that's getting easier (and you can always do it manually from source without ill effect).
for ad-supported software which states the following:
Hey, we're going to install software on your machine that pops up advertisements whenever you do anything on the internet, and sometimes when you're not! Also, we'll record all the sites you go to. Hope you don't mind!!!! LOL
Let's face it, none of the CPUs used in common Unix-specific systems (PowerPC, UltraSPARC, Itanium, SHA-x) are close to RISC. All of them have relatively deep pipelines, interlocking stages and some form of microcode. Only the MIPS processors can be considered close, but still, nothing like the original RISC ideals.
(The other way you can express this is few chips are really CISC either. x86s aren't CISC, they're just Gimp-IA'd)
A red-hat based distro can last a long time provided you use somewhat more sophisticated tools to manage it. Suggestion: apt-rpm.
I don't know what those other problems you speak of stem from, for I have many RedHat boxes and have not experienced them. Perhaps the admins are idiots?
A Solaris box is also difficult to work with on the first go-round. Usually you get sent to Sun classes and everything becomes clear.
One of the big things about UML...
on
UML Fever
·
· Score: 1
was that it was supposed to be heavily utilized by CASE tools. And the OMG never sat down and wrote a standard serialization format for it? That was an enormous blunder.
Currently your best bet is to store them in Rational file formats and hope everyone else has Rational.
You're the founder of a town in the wild American west just before the peak of the gold rush. Like the HBO show, you'd play the role of a bad guy. You're objective is to make a whole bunch of money before 1) the town revolts agaisnt you 2) the local budding government gets a whiff that you're town is worth paying attention to (taxable). Of course you can kill people who oppose you (but do it quietly) and you can bribe officials, so you just need to not screw up.:-)
It'd be a cross between a RTS and an RPG. Slower paced RTS with more RPG-like detail.
I think the rough-and-tumble western style could seriously kick ass.
those games were intended to be Mad Max tie-ins but the publisher couldn't afford the fees to license the movie properties. So they had to keep them generic (but obviously inspired by it)
...your iPod and/or iTunes key. QuickTime doesn't work on linux (officially) but playfair can still talk to the iPod over your firewire in that particular instance.
Slashdot Mirror
Or the Rage XL AGP card? Or a Matrox?
You act like don't have low cost, low power options for non-gaming use.
But what NineNine "expects" is unreasonable. I think the combination of paid support/access with ability to see and modify the source for a POS system is great! But no one should be expected to develop such a monstrosity just to do it, especially when there's no reasonable way the developer can test or deploy it!
I mean, do you have POS cash registers in your basement just waiting to be endowed with such an application? Come on.
I mean seriously. It bundles in plausible deniability into the network protocol. Stuff that into your pipe and smoke it.
If you want to do skunkworks-style development, collaboration, or your just an 'ARRRRR net pirate then WASTE is a tasty morsel of goodness that is hard to find in other products.
Point of sale system, right. You don't do that open source because there's no point. Who'd use it that doesn't have a purchasing department and thus can be expected to outlay a little dough?
and I'm going to feed a used tampon down your fucking throat.
At first I got tired of the slashdot groupthink against MS. Now I'm tired of the slashdot anti-groupthink MS apologists.
Would you please stop replying in these threads unless you can put the article into a useful context instead of slinging shit around.
Also, catch SARS. Thanks.
Get a life.
As of late any time someone wants to look "smart" or "insightful" they post a link to linuxsecurity.org in response to a inane comment about Windows security. You take a site which wants to be honest about security issues in free OSs and use it as some kind of childish comeback.
Real good sleuthing there, Sherlock.
The only thing you've done is start a pissing contest. Just don't reply to posts that don't need replying to. The parent wasn't making an argument, but a joke. You should know that we bash Microsoft here, whether they deserve it or not, AND EVERYBODY KNOWS THAT. It's not like they need to be actively defended.
What's interesting about the 3 bugs, DIPSHIT, is that they were discovered by eEye (and others) some time back in late 2003 and they sat on their hands waiting for Microsoft to publically acknowledge them and release patches.
Meanwhile all of the listings on that front page are fresh and current, and advise you to disable services there aren't already patches for. So sit and spin, my friend.
the compression is software-based, so they can claim any compressed number they want, depending on what they are compressing. It has nothing to do with the medium.
I've always bought ZIP 250 (IDE, not SCSI) and have never had a problem. I've heard people bitch about the 100s but the price difference was never more than $15 and I never regretted that. Of course, now I just use USB keys. ^_-
Clearly some distribution with a moderate following has to stand up and say: "We will cater to the desktop realm" and they want capital to bring in HCI brains and work on bringing that stuff into line.
And I'm not just talking abotu Helix or Lindows or Lycrosis here.
I mean Helix is Novell/Suse and they apparently don't have the cash for that now. Lindows is in it for the money, not advancing the state of the art.
So who else can step up to bat?
I don't know, we haven't terraformed the seabed very much. I thought deep water was the real last frontier of earth.
And then how do you classify x86_64? Itanium?
;-D
I think you should just specify the platform. They (being those "other guys") only in it together against Intel x86. But if you want to argue platform features you have to be more specific than RISC (or "not x86") because they are not all created equal.
Specifically Intel's own new baby (Itanium2) probably has them panting and wheezing, with Power close behind. So... I don't know.
And all of them run Java slowly.
I have a scary notion that a port of Mono would be end up working better on Unix/XYZ compared to Wintel.
GDM, Xauth and XFree do that because they like gethostbyname to figure out what to do. Best solution to prevent any rough spots during a network reconfigure is to just add the hostname(s) to the loopback interface line in your hosts file, which circumvents any IP addy / hostname / DNS issues.
The scripts have gotten a lot better since the pre-8.0 days. A lot of what was once shell scripts is now written in python with better error handling and re-use of common components. Not perfect, but some things, even the existing shell scripts (/etc/sysconfig/network/ifup-xxx for example) are downright pleasant to hook into and abuse.
Now, in my experience what people call RPM hell has always been a PEBCAK (no offense). RPMs are trackable and verifiable, more recently allow transactions and rollbacks, and lots of other goodies that few people want to learn how to use.
Whenever you get stuck (often by a package maintainer's mistake in dependancies), the solution is almost always to build a needed RPM from source, but editing the spec file to remove the dependancies that conflict (but you KNOW are satisfied). If you know what you want, but can't get it to work, then you can force it without breaking consistency checks and carrying that shit forward. And uninstalling packages is not a bad thing (it doesn't clobber configuration files). You can back out of conflicting ones and repackage them into RPMs, this way you don't have to download them again later.
I mean really, the one-service-per-machine thing is a crock. You're telling me you can't simultaneously use postfix and apache on a machine installed from RPMs at once succesfully? What combinations of services have you found that don't mix? Come on, give me a break with the hyperbole.
The thing about Solaris is that they've got a much smaller target they need to worry about (limited hardware to support [no LAPTOPS], no catering to content creation/gamers, etc.). So of course they can make a very firm foundation... it's setup from the get-go to handle every type of machine it can be installed on and most every workload out of the box. You have to go out of your way to render the machine "barebones".
That being said, I like them. I like RedHat boxes too (just a little bit more, but not much). Hell, and SuSE is dandy too. Gosh darn it, I can even tolerate a Windows 2003 box.
Well, that's my spiel.
apt for rpm is NO DIFFERENT than apt tooled for pkg. Moreover, with apt on RPM based systems I have a choice of (well last time I modifed sources.list) 8 different repositories for my package sources (source + binary) with various different political bents and countries of origin, so I get EVERYTHING. ::glee!!!::
/etc/sysconfig and the like. Also the installer and hardware detection is _tight_. (cliche, but 100% true). The only thing that still rubs me the wrong way is trying to patch kernel source RPMs, but that's getting easier (and you can always do it manually from source without ill effect).
You've obviously never used RedHat long enough to appreciate it. You get used to the layout of
nt
for ad-supported software which states the following:
Hey, we're going to install software on your machine that pops up advertisements whenever you do anything on the internet, and sometimes when you're not! Also, we'll record all the sites you go to. Hope you don't mind!!!! LOL
Let's face it, none of the CPUs used in common Unix-specific systems (PowerPC, UltraSPARC, Itanium, SHA-x) are close to RISC. All of them have relatively deep pipelines, interlocking stages and some form of microcode. Only the MIPS processors can be considered close, but still, nothing like the original RISC ideals.
(The other way you can express this is few chips are really CISC either. x86s aren't CISC, they're just Gimp-IA'd)
A red-hat based distro can last a long time provided you use somewhat more sophisticated tools to manage it. Suggestion: apt-rpm.
I don't know what those other problems you speak of stem from, for I have many RedHat boxes and have not experienced them. Perhaps the admins are idiots?
A Solaris box is also difficult to work with on the first go-round. Usually you get sent to Sun classes and everything becomes clear.
was that it was supposed to be heavily utilized by CASE tools. And the OMG never sat down and wrote a standard serialization format for it? That was an enormous blunder.
Currently your best bet is to store them in Rational file formats and hope everyone else has Rational.
Criminal.
The premise:
:-)
You're the founder of a town in the wild American west just before the peak of the gold rush. Like the HBO show, you'd play the role of a bad guy. You're objective is to make a whole bunch of money before 1) the town revolts agaisnt you 2) the local budding government gets a whiff that you're town is worth paying attention to (taxable). Of course you can kill people who oppose you (but do it quietly) and you can bribe officials, so you just need to not screw up.
It'd be a cross between a RTS and an RPG. Slower paced RTS with more RPG-like detail.
I think the rough-and-tumble western style could seriously kick ass.
Holy shit I would so buy that game. I'd even play it on Saturday.
those games were intended to be Mad Max tie-ins but the publisher couldn't afford the fees to license the movie properties. So they had to keep them generic (but obviously inspired by it)
built in work-surface if it has sliding rails. Usually access to components is extremely easy. This is great if you're in hardware tinker mode.
...your iPod and/or iTunes key. QuickTime doesn't work on linux (officially) but playfair can still talk to the iPod over your firewire in that particular instance.
I don't have OSX. Therefore I don't have access to the Quicktime developer tools/libraries. I have a windows box without MSVC, solaris, and linux.
/dev/kmem to pull the decrypted version of the AAC from memory.
So what are my options?
1) Use wine and the QT dlls from windows together with
2) Out to CD and back (not entirely bad, but kinda clumsy)
3) playfair
I like #3. I'm very happy with it. The extant tools are much more clumsy than this simple, direct method.