All the Openosx folks were doing was redistributing the packages the Fink project had made with Installer.app targets Did I get it right? Eh? It's on the Fink website; go take a look.
Unless the packages themselves are GPLed (unlikely, and likely not enforcable) the only violation would be not distributing source.
Now, I've not used the Fink packages, but if Christoph had added himself to the list of authors after patching the apps to run on OS X, then the Openosx folks *removed* said reference, then yeah, that'd be a violation.
I'll have to pore through the GPL tonight, but AFAIK there's no violation here...Christoph wants credit for porting, basically. AFAIK that's not required and for it to be required Christoph would have to slap on an advertising clause in his copy of the GPL, which would a.) be a violation of the GPL and b.) would require special permission from all the authors of said ported software.
You can call me a troll if you like, but the endless hypocrisy and general bad attitude shown by many of you has chased more than just me away from your favorite OS. I have no interest in being ridiculed for admitting that Linux is not the best choice for every job.
Along with the alleged security holes in glibc (which most fBSD wonks can't seem to point out, despite saying they're there), the "excessive code bloat" (c'mon, let's get real here. Let's look at hardware support in fBSD, then in Linux, and then we'll talk about the codebase size) the alleged poor performance of Linux 2.4 kernels (Sysadmin showed this to not be the case; Linux systems still outperform fBSD machines overall) and the alleged poor management of Linux development overall.
Call it what you want, but I call it FUD.
I have no interest in being ridiculed for admitting that Linux is not the best choice for every job.
Agreed! However, I don't personally plan to start up a new Yahoo! so I don't need FreeBSD. For desktop machines, Linux outperforms FreeBSD. Sorry, but it's true. And yes, I've been an off-again, on-again FreeBSDer.
Of course, there are more concrete reasons why I don't use Linux as well, but my dislike of the community that I would be forced to deal with is a big part of my allegance to the BSDs. The Debian zealots are by far the worst and I would almost rather watch FBSD die than have it absorbed into the circlejerk.
For a real circlejerk, fire up your favorite IRC client, head for irc.linux.org (Openprojects) and hop into...#freebsd. Bonus if you get a kickban for asking questions about Linux compatibility (FreeBSD is not Linux!)
And it's not just #freebsd on OPN. Daily Daemonnews, FreeBSD Diary, FreeBSDzine...you name it. Many of the stories I've seen either are about "oh look, we're so much l33ter than Linux" or are loaded with comments by people creaming their jeans over FreeBSD.
And I didn't see people running to the press when a FreeBSDer stole code from the Linux kernel recently (bttv?) Apologists have even excused it ex post facto by stating that, hey, a Linux user stole BSD code without putting the required copyright notice on it (which has since been done, BTW.)
Come on. Let's get real here. Community matters . . . to a certain extent. The general attitude of developers is what should matter the most. Heck, I recently became one of those Debian folks after having used FreeBSD for a few months. I don't miss it a bit, to tell you the truth.
Which is exactly the problem with patents. I think that if TiVO can show that they created this idea without knowing about the patent (which doesn't sound hard as it sounds like the "pause" company was sitting on it) that they should be able to get a co-patent (or something) on the idea.
Yup. I had this weird idea of doing non-destructive video compression a while back, and when all was said and done, I did a search of abstracts and at least two things I came up with on my own were patented by Thompson.
It's getting fucking ridiculous. The problem isn't really patent-squatters; in that respect, the system is actually working "as advertised." The problem is that patent offices push through anything with sufficient technobabble (like the aforementioned pausing-of-live-tv concept.)
Wow, I wonder if you would have said that before this annoucement.
Don't know about the original poster, but I would have. Lots of nice features that other clients lack. On the worst end, I'd put Mactella. I use LimeWire at home on my Linux box, and at work on my Mac box. Nice li'l app.
Like many other closed-source Java apps, LimeWire is prepackaged for different platforms to make it easier for one to install the client on various platforms. For Linux, one gets a nice Bash script that allegedly makes running LimeWire easier.;-) Similarly, the MacOS version has a nice installer and a nice script that makes starting the client much easier to start up.
Hope not to find this kind of automation with ports.
Not as automated, no. If you want to take a stab at FreeBSD Ports, I'd recommend FreeBSD. However, if you currently use Linux as a workstation OS, I wouldn't recommend it.:-)
It's wonderful for stable systems. It runs a number of large-scale websites. The very organizational structure is in place and has a goal of producing a stable, secure OS. Not supporting 10,000 different processors, not throwing the newest shit in the kernel. It's kinda like having Debian Stable as the base.
OTOH, Ports is kinda like Debian Sid. It's amazing how up-to-date a lot of the software is in the Ports tree. And the neato thing about ports (IMHO) is that, in many cases, aside from the patches that are applied, sources are downloaded from either the main software distribution site or a mirror, rarely from a centralized archive (as is the case with Debian and many other Linux distributions.)
One thing I had terrible luck with, aside from the fact that 3D DRI support is next to nonexistent, was soundcard support. Trying to play MP3s in XMMS was painful. It was for that reason that I switched to using Debian Sid with a patched kernel (for ext3 support.)
Bah. I have a machine with Win98 and Linux. Never have troubles with Linux. Even after paring down services to a bare minimum, I still have problems.
And, guess what? Yes, the AC is right. I have "crap" hardware. If nobody in Redmond can be bothered to help the hardware manufacturers work with the OS, I don't have time for the OS. If the solution is "don't buy 'crap' hardware," then fuck it, who needs the OS? The OS is there to act as a proxy between my hardware and my software. If it won't work with the hardware, and the only solution is "buy new hardware, and not just any hardware," then it seems to me that MS's vision to be the desktop OS has failed. Period.
I wonder what the goal is of dening the Free Software Foundation credit for things such as the GPL and kicking off gcc, etc.?
Alienation, at this point (at least in my eyes.) It's gone beyond getting credit. The LGPL even contains language that claims that Linux is merely a variant of the GNU operating system. Nevermind that much of that GNU software (most notably glibc) was ported to Linux.
Overhauling X in general? Just steal display PDF from Apple/Adobe?
You might check into Display Ghostscript (uh, dunno if it can handle Display PDF stuff...yet...:-) or you might just want to check into the X extension that the current QT, future GTK+, and this current theme/lib uses, which is Xrender.
That's the funniest thing I've read in months. Ever do a stint at MS's marketing division? Linux Is Going Down, y'know.
/me changes into a dry pair of pants...was it raining just then?
If your definition of "maintain" is "moronically install stuff until the hard drive is full, then re-install Windows when I start having problems with the OS" and your definition of maintaining Linux is "hacking the kernel not from source, but with a hex editor" then yeah, Windows is much easier to maintain.
I'm not sure who you're trying to impress...I guess the "smart" people who switched back to Windows when they couldn't get Red Hat to work on their Presarios. Sad for them, sad for you. No, no, don't learn more about Linux and certainly don't help get support for your machines; dump Linux for being "crap" and go with the platform that "r00lz". j00r such l33t d00dZ!
Not upside down at all. You've just not been around long enough.:-)
At one point, the best way to get a great X server was to buy one. Always struck me as somewhat stupid to have to buy one when I'd be paying more money for the server than I did for the card (I once priced an X server, don't remember if it was Metro, Xi, or what) and it would have run me $150. The card in question was $50. Part of the price of that card was to help pay for the development of Windows drivers, of course.
So get off your ass if you don't like it and start a Free project. This is based on WINE, after all.
Gee, want to have everything MacOS has without modifying the underlying OS to support resource forks?
1.) make sure apps hide file extensions, preferring, instead, icons
2.) Hell, UNIX people use extensions like.tar.bz2 to signify bzip2'd tar files, right? Get ready for 8bim.tif. (for anyone curious, 8bim is the creator code for Photoshop docs on a Mac.)
Really, there's the wonderful, superior data you get on a Mac when dealing with a Photoshop TIFF. "8bim" as the creator code (huh?) and the more sensible "tiff".
Sure, sounds great. *rolls eyes*
Sure, feel free to rip me a new one if I didn't use the proper terminology. I mess with ResEdit maybe once a year.:-P
Bah, everyone's ignoring a couple of important points:
1.) Software such as glibc wasn't just compiled on linux. It was ported, shoe-horned in if you will.
2.) The license under which glibc was re-released under, 2.1, has a clause about the GNU operating system, or its variant, GNU/Linux. What the devil? Variant? Variant???!?
Give some determined programmers some time, and those GNU utils could be replaced. And, much as anyone hates to admit it, the compiler could be replaced too. Prepare for BSD/Linux, y'all.
If you can't figure out how to keep from installing X when you're installing Mandrake, you have no business running Debian.
Seriously.
Re:Therein lies the dilemna
on
Mac Rants
·
· Score: 2
Bah, I hadn't replied in a while because I've been too busy at work...and it's an all-Mac house, I'll have you know.
Seen the numbers lately? In raw numbers MacOS
Oops, there aren't very many! And the few viruses that DO exist for mac don't spread by email, don't spread as far or fast, and don't tend to do as much (if any) damage.
Give it time. I haven't checked out Outlook Express for the Mac, but if it does allow executables to run, you can bet that some smartass will write a nice VBScript "virus" (damn, I didn't realize that idiots running untrusted code constituted a "virus") and it'll make very few waves, because MacOS isn't popular.
Just wait until OS X is popular. Idiots running their systems wide-open with loads of network services will complain about "hackers."
Startup test, from blackbox, showed konqueror to be the clear loser. Well, duh, kdeinit wasn't running yet! A fairer test would have been in in konqueror's "native environment."
Hey, at least I didn't post a lame joke about the obvious misspelling. Get a life, people, willya?
Stop spamming Slashdot with propaganda about your site!
Oh, you say it's not your site, but since users vote on stories themselves, it is your site, goddamnit. Stop spamming other sites with k5 propaganda unless you consider k5 to be fair game for crapfloods and spamfloods (one and the same, I say)
Can't say the hardware's too slow, but yeah, the damn things are too expensive. If they'd had a lick of sense, they'd have been on the x86 platform years ago. Oh wait, that's what the Star Trek project was all abour, right? Feh, then again, they'd go from having fat binaries to fatter binaries to support the x86 platform rather than trying to work on something else, like a nice virtual machine that would eliminate the need for fat binaries.
But what the hell do I know.:-)
Re:Therein lies the dilemna
on
Mac Rants
·
· Score: 2
I was particularly amused by the rant's dismissal of Mac's lower risk from viruses. Yes, Macs can't run x86 code, and if the Mac had a bigger market share, it would probably have a bigger virus share--but is that relevant to a buying decision?
Well, sure. I buy x86 machines to be safe from MacOS viruses.
Slashdot Mirror
True, but...
All the Openosx folks were doing was redistributing the packages the Fink project had made with Installer.app targets Did I get it right? Eh? It's on the Fink website; go take a look.
Unless the packages themselves are GPLed (unlikely, and likely not enforcable) the only violation would be not distributing source.
Now, I've not used the Fink packages, but if Christoph had added himself to the list of authors after patching the apps to run on OS X, then the Openosx folks *removed* said reference, then yeah, that'd be a violation.
Eh, let him resign. Who needs crybabies?
In his email, he mentions releasing, say, Red Hat Linux with a few changes and no mention of RH, which would be okay. Not nice, but okay.
Can anyone point out the GPL violation, or is this another Slashdot fuckup?
ext3 was just about the only reason I was using -ac kernels...
Along with the alleged security holes in glibc (which most fBSD wonks can't seem to point out, despite saying they're there), the "excessive code bloat" (c'mon, let's get real here. Let's look at hardware support in fBSD, then in Linux, and then we'll talk about the codebase size) the alleged poor performance of Linux 2.4 kernels (Sysadmin showed this to not be the case; Linux systems still outperform fBSD machines overall) and the alleged poor management of Linux development overall.
Call it what you want, but I call it FUD.
I have no interest in being ridiculed for admitting that Linux is not the best choice for every job.
Agreed! However, I don't personally plan to start up a new Yahoo! so I don't need FreeBSD. For desktop machines, Linux outperforms FreeBSD. Sorry, but it's true. And yes, I've been an off-again, on-again FreeBSDer.
Of course, there are more concrete reasons why I don't use Linux as well, but my dislike of the community that I would be forced to deal with is a big part of my allegance to the BSDs. The Debian zealots are by far the worst and I would almost rather watch FBSD die than have it absorbed into the circlejerk.
For a real circlejerk, fire up your favorite IRC client, head for irc.linux.org (Openprojects) and hop into...#freebsd. Bonus if you get a kickban for asking questions about Linux compatibility (FreeBSD is not Linux!)
And it's not just #freebsd on OPN. Daily Daemonnews, FreeBSD Diary, FreeBSDzine...you name it. Many of the stories I've seen either are about "oh look, we're so much l33ter than Linux" or are loaded with comments by people creaming their jeans over FreeBSD.
And I didn't see people running to the press when a FreeBSDer stole code from the Linux kernel recently (bttv?) Apologists have even excused it ex post facto by stating that, hey, a Linux user stole BSD code without putting the required copyright notice on it (which has since been done, BTW.)
Come on. Let's get real here. Community matters . . . to a certain extent. The general attitude of developers is what should matter the most. Heck, I recently became one of those Debian folks after having used FreeBSD for a few months. I don't miss it a bit, to tell you the truth.
Yup. I had this weird idea of doing non-destructive video compression a while back, and when all was said and done, I did a search of abstracts and at least two things I came up with on my own were patented by Thompson.
It's getting fucking ridiculous. The problem isn't really patent-squatters; in that respect, the system is actually working "as advertised." The problem is that patent offices push through anything with sufficient technobabble (like the aforementioned pausing-of-live-tv concept.)
The fact that OS X is based on FreeBSD may very well keep this hole from becoming as damaging as it is on Windows.
Wow. Amazing what's "Insightful" these days. Check yo' facts, Buran. FreeBSD != BSD. MacOS X != FreeBSD. They're both BSDs, though. Get it?
Don't know about the original poster, but I would have. Lots of nice features that other clients lack. On the worst end, I'd put Mactella. I use LimeWire at home on my Linux box, and at work on my Mac box. Nice li'l app.
Like many other closed-source Java apps, LimeWire is prepackaged for different platforms to make it easier for one to install the client on various platforms. For Linux, one gets a nice Bash script that allegedly makes running LimeWire easier.
Hope that clears things up a bit.
Not as automated, no. If you want to take a stab at FreeBSD Ports, I'd recommend FreeBSD. However, if you currently use Linux as a workstation OS, I wouldn't recommend it.
It's wonderful for stable systems. It runs a number of large-scale websites. The very organizational structure is in place and has a goal of producing a stable, secure OS. Not supporting 10,000 different processors, not throwing the newest shit in the kernel. It's kinda like having Debian Stable as the base.
OTOH, Ports is kinda like Debian Sid. It's amazing how up-to-date a lot of the software is in the Ports tree. And the neato thing about ports (IMHO) is that, in many cases, aside from the patches that are applied, sources are downloaded from either the main software distribution site or a mirror, rarely from a centralized archive (as is the case with Debian and many other Linux distributions.)
One thing I had terrible luck with, aside from the fact that 3D DRI support is next to nonexistent, was soundcard support. Trying to play MP3s in XMMS was painful. It was for that reason that I switched to using Debian Sid with a patched kernel (for ext3 support.)
And, guess what? Yes, the AC is right. I have "crap" hardware. If nobody in Redmond can be bothered to help the hardware manufacturers work with the OS, I don't have time for the OS. If the solution is "don't buy 'crap' hardware," then fuck it, who needs the OS? The OS is there to act as a proxy between my hardware and my software. If it won't work with the hardware, and the only solution is "buy new hardware, and not just any hardware," then it seems to me that MS's vision to be the desktop OS has failed. Period.
Alienation, at this point (at least in my eyes.) It's gone beyond getting credit. The LGPL even contains language that claims that Linux is merely a variant of the GNU operating system. Nevermind that much of that GNU software (most notably glibc) was ported to Linux.
You might check into Display Ghostscript (uh, dunno if it can handle Display PDF stuff...yet...
If your definition of "maintain" is "moronically install stuff until the hard drive is full, then re-install Windows when I start having problems with the OS" and your definition of maintaining Linux is "hacking the kernel not from source, but with a hex editor" then yeah, Windows is much easier to maintain.
I'm not sure who you're trying to impress...I guess the "smart" people who switched back to Windows when they couldn't get Red Hat to work on their Presarios. Sad for them, sad for you. No, no, don't learn more about Linux and certainly don't help get support for your machines; dump Linux for being "crap" and go with the platform that "r00lz". j00r such l33t d00dZ!
At one point, the best way to get a great X server was to buy one. Always struck me as somewhat stupid to have to buy one when I'd be paying more money for the server than I did for the card (I once priced an X server, don't remember if it was Metro, Xi, or what) and it would have run me $150. The card in question was $50. Part of the price of that card was to help pay for the development of Windows drivers, of course.
So get off your ass if you don't like it and start a Free project. This is based on WINE, after all.
1.) make sure apps hide file extensions, preferring, instead, icons .tar.bz2 to signify bzip2'd tar files, right? Get ready for 8bim.tif. (for anyone curious, 8bim is the creator code for Photoshop docs on a Mac.)
2.) Hell, UNIX people use extensions like
Really, there's the wonderful, superior data you get on a Mac when dealing with a Photoshop TIFF. "8bim" as the creator code (huh?) and the more sensible "tiff".
Sure, sounds great. *rolls eyes*
Sure, feel free to rip me a new one if I didn't use the proper terminology. I mess with ResEdit maybe once a year. :-P
1.) Software such as glibc wasn't just compiled on linux. It was ported, shoe-horned in if you will.
2.) The license under which glibc was re-released under, 2.1, has a clause about the GNU operating system, or its variant, GNU/Linux. What the devil? Variant? Variant???!?
Give some determined programmers some time, and those GNU utils could be replaced. And, much as anyone hates to admit it, the compiler could be replaced too. Prepare for BSD/Linux, y'all.
True. Aside from the compiler, Linus could have ripped the kernel outa BSD and had a grand ol' time. That leaves the problem of the compiler. :-)
If you can't figure out how to keep from installing X when you're installing Mandrake, you have no business running Debian.
Seriously.
Seen the numbers lately? In raw numbers MacOS
Oops, there aren't very many! And the few viruses that DO exist for mac don't spread by email, don't spread as far or fast, and don't tend to do as much (if any) damage.
Give it time. I haven't checked out Outlook Express for the Mac, but if it does allow executables to run, you can bet that some smartass will write a nice VBScript "virus" (damn, I didn't realize that idiots running untrusted code constituted a "virus") and it'll make very few waves, because MacOS isn't popular.
Just wait until OS X is popular. Idiots running their systems wide-open with loads of network services will complain about "hackers."
Hey, at least I didn't post a lame joke about the obvious misspelling. Get a life, people, willya?
Oh, you say it's not your site, but since users vote on stories themselves, it is your site, goddamnit. Stop spamming other sites with k5 propaganda unless you consider k5 to be fair game for crapfloods and spamfloods (one and the same, I say)
But what the hell do I know.
Well, sure. I buy x86 machines to be safe from MacOS viruses.