Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Unix Operating Systems Software BSD

Ports System As A Strategy Against .NET? 170

proclus writes: "The FreeBSD ports system has been ported to Mac OSX, GNU/Linux, LinuxPPC, and OpenBSD. Check out this descriptive paper and roll your own ports-based distribution." Besides an some informative description of the mechanics of the port system, the paper lays out the case for ports (free and readily available) as a good antidote for .Net and other subscription-based systems.
This discussion has been archived. No new comments can be posted.

Ports System As A Strategy Against .NET?

Comments Filter:
  • by Anonymous Coward
    We should all keep in mind this simple truth: Slashdot's BSD section is dying.
    You don't need to be Kreskin to predict Slashdot's BSD section's future. The hand writing is on the wall: Slashdot's BSD section faces a bleak future. In fact there won't be any future at all for Slashdot's BSD section because Slashdot's BSD section is dying. Things are looking very bad for Slashdot's BSD section. As many of us are already aware, Slashdot's BSD section continues to lose market share. Red ink flows like a river of blood.

    Let's keep to the facts and look at the numbers.

    BSD section reader, Anonymous Coward, states that there are 7 readers of Slashdot's BSD section. How many readers of Slashdot's BSD section are there? Let's see. The number of BSD versus Linux posts on Usenet is roughly 200, 50% lower than last year, which was 50% below the year before. In 1999, there were a known 28 readers of Slashdot's BSD section. This is consistant with the figures provided by Anonymous Coward.

    Additionally, the number of "*BSD is dying" posts has been on the rise. In 1999, there were 2000 "*BSD is dying" posts, which rose to 4000 in 2000, and a staggering 8000 in 2001. This is consistant with the number of Usenet posts and is clear evidence that Slashdot's BSD section is dying.

    All major surveys show that Slashdot's BSD section has steadily declined in market share. Slashdot's BSD section is very sick and its long term survival prospects are very dim. If Slashdot's BSD section is to survive at all it will be among OS hobbyists, dabblers, and dilettantes. Slashdot's BSD section continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Slashdot's BSD section is dead.
  • by Anonymous Coward
    "...GNU/Linux, LinuxPPC..."

    Just because it's on the PowerPC does not stop LinuxPCC from being a GNU system.

    Wouldn't 'GNU/Linux-x86' and 'GNU/Linux-PPC' be more fitting?

  • by Anonymous Coward
    .NET is a virtual machine. You don't subscribe, although the VM will make it easier to support these types of business models.
  • by Anonymous Coward
    The gentoo linux distro (www.gentoo.org) has a package management system similar to FreeBSD ports, fyrc.
  • by Anonymous Coward
    Yeah yeah yeah. Don't we know all those ideas already? It's not new.

    What is new is this. North America's in a recession. Micrsoft's trying to ensure a steady stream of money for itself. IT is also trying to do a million things at the same time.

    From launching the Xbox to introducing "Upgrade Advantage" down people's throats and bringing out C# then .NET and fighting a court battle. What's more they are really stuck without ideas for some really useful new features for their Office Suite and OS.

    With this new subscription model they hope to force upgrades ( which should be free ) and so have greater control over what you run. I mean if every new release of windows breaks compatibility with "unwanted software" it's pretty hard to sell your stuff eh?

    Why would business want to jump into bed with .NET? So MS can ass rape them? .NET for large internet companies means ripping out thier currnet setup and paying more money for something that's not even proven yet. And having the newest versions of Office and word for "free" isn't what you always want. Retraining and getting thrid party software remade for the new platform is a real pain and it's not at all useful for many companies.

    Personally I don't see Microsoft as being in a very strong posisiton right now.
  • by Anonymous Coward
    look at this site for info: http://www.freebsd.org/doc/en_US.ISO8859-1/books/p orters-handbook/index.html
  • Passport is a unified authentication system, not a subscription-based service.

    You are thinking of Hailstorm.

    Actually I'd say Hailstorm is possible because of .Net, not really part of .Net.

  • by evand ( 2571 ) <(ude.umc) (ta) (dse)> on Wednesday July 04, 2001 @09:26AM (#108510) Homepage

    It does, although IIRC building dependencies for the source isn't really a stable feature yet. From the man page for apt-get:

    source causes apt-get to fetch source packages. APT will examine the available packages to decide which source package to fetch. It will then find and download into the current directory the newest available version of that source package. Source packages are tracked separately from binary packages via deb-src type lines in the sources.list(5) file. This probably will mean that you will not get the same source as the package you have installed or as you could install. If the --compile options is specified then the package will be compiled to a binary .deb using dpkg-buildpackage, if --download- only is specified then the source package will not be unpacked.

    A specific source version can be retrieved by postfixing the source name with an equals and then the version to fetch, similar to the mechanism used for the package files. This enables exact matching of the source package name and version, implicitly enabling the APT::Get::Only-Source option.

    Note that source packages are not tracked like binary packages, they exist only in the current directory and are similar to downloading source tar balls.

    However, that will only download/build/install the one source package. If one wants to install the packages required to satisfy the build dependencies for a given source package, the build-dep option should be used with apt-get.


  • You don't wanna build from source, you say? Grab the package then and play the dependency game again


    Actually a line like this will get all dependencies automagically the same way the ports collection does:

    pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/A ll/mypackage.tgz

    I like to build from ports for things that need a whole lot of customisation (say mod_php). But for things like gimp that are pretty generic, I'll grab the binary packages because its a whole hell of a lot faster. (Yes even faster than compiling on my 1ghz Athalon.)

    Every time I think that FreeBSD has let me down, I find out that I was just stupid.


    -Peter

  • What's wrong with grabbing a source package and doing rpm --rebuild? Okay, that's two steps instead of one, but it's not that much of a big deal.

    If apt could download source packages, resolve dependencies, and install, that would be perfect. You could even unpack each source package in some special system-wide 'ports' directory for those who think having the whole source tree in one place is cute.
  • unfortunatly there has been many offerings of free software in the past. Do people use it over commercially available software? Are people flocking to Linux over MS b/c it is free?

    No.

    People go w/the mass. We are the crazy ones (smart?)

    It's unfortunate but true.
  • I don't think that what MS is doing is "ignorant". It is money. ignorance != money.
  • WTF!!! That gets moderated as flamebait!

    Heaven forbid I corrected somone who was factually incorrect. Just imagine if people who were wrong started being corrected. We would get a more informed slashdot community, and people might start checking basic facts before posting. Good thing I was moderated as flamebait before I caused real damage.

    Ben
  • For a company so evil, at least they're extending a hand, but according to some this is viewed as MS looking to stir up troubles in the open source community.

    Extend a hand? What do you think this is, diplomacy? Microsoft is doing what is in their best interest, and right now that is making use .net gains wide acceptable. If people view it as a Microsoft only solution, it won't gain that. Having it run on BSD will make people more secure in writing for .net because it isn't just a windows thing anymore.

    It is sort of analogous to front page extentions. Sure, Microsoft ported their frontpage extentsions to Unix. Was it altruism? No! It was neccisary to gain acceptance.

    So don't tell me "a company so evil" or "they're extending a hand" - Microsoft is not trying to be your best friend. They are not an a x-girlfriend after a difficult break up. Microsoft is another self-interested pragmatist and if it suits them they will port their software, but it is totaly unrealated to "extending a hand" or being "less evil".

    Ben
  • Trith writes: The thing that makes Java WORA is the fact that the API goes with the language and the runtime enviroment. C# will be providing two of the three, the Runtime and the language.

    You are misinformed.

    .NET Common Language Infrastructure includes the .NET Framework Class Library. They have names like system.net and system.io whatever, so it feels a lot like Java's libraries.

    Ben
  • by bhendrickson ( 7671 ) on Wednesday July 04, 2001 @08:55AM (#108518)
    What does this have to do with .NET; I assumed there would be some kind of intermediate code base or something. But all I see is an open platform.

    I suggest that "c" is functioning as the intermediate language. Following me on this one.

    When is .Net bytecode going to get compiled down for applications? Such large applications are suppose to be converted to native during the install. When are these BSD packages convered to native? Well, one can do it when one installs a program (one could also grab a pre-compiled binary for one's specific system if available, but one doesn't have to).

    What does distributing in the source code gain? The ability to check for security problems and to compile down to one's specific systems. What does distributing in the byte code get? The ability to check for security (by having a logical sandbox) and compile down to one's specific system.

    So I suggest the use of .net's bytecode is really rather analogous to the free software communities' use of source code. So in practice, this set of highly portable software depending on parts of FreeBSD as a "runtime" is a system that is offering many of the same benfits as the .net platform.

    I suspect Timothy was meaning some simular.

    Ben
  • I agree, not merging needed changes back into the real source, even if they are "just" for makefiles (!), is asking for big trouble. Most of the time, those kinds of changes can be effected through the configure scripts.
  • Comment removed based on user account deletion
  • Comment removed based on user account deletion
  • This will only make your job that much easier for the next release

    Perhaps someone at Red Hat doesn't want their job to get easier (i.e. job security).


    ---
  • .NET is an end-to-end environment geared towards producing subscription based software... (and preferably locking you into subscription to _microsoft_ software) It doesn't really make it easier or harder to code stuff on windows (except for they updated, and slightly more logical APIs, over win32's utter crud (CALLBACK anyone?)).

    Technologies like XML and SOAP make it easier for companies to provide "services" over the internet - but, what if they provided a service and nobody came? To put it another way, what's the point in allowing people to "lease" software, if they're not going to use, because us Free Software people are giving it away for free? FreeBSD ports is a wonderful distribution system.

  • Most patches (not all) in a port are only there to get the package to build on a specific system. They would be totally useless elsewhere. And most have nothing to do with the code itself.

    Case in point: net-snmp on FreeBSD-4.3. The majority of patches are to makefiles. The majority of the rest only updated the FreeBSD version macros. Actual code changes are rare, and are only for the purpose of getting the software to build.

    You are not like all other developers. We all work in different ways. I develop on FreeBSD and Slackware. If a patch came in for HPUX, I wouldn't accept it. It would be pointless to do so. I cannot test it, and cannot maintain it. Unless it were an actual bug fix, I would ignore it. If the HPUX maintainer is willing to do the work I'm more than happy. I'll add him to my update mailing list along with a thank you note and a virtual beer.
  • And with the official CDs, you get thousands of precompiled packages all ready to run with no download. It doesn't take a Kreskin to know that some people will grasp at any straw in an effort to bash someone else's OS.
  • It's Darwin plus all the GNU stuff.

    FreeBSD, from which Darwin was in part based, also contains all of the GNU stuff. I am assuming that GNU-Darwin is still using the Mach microkernel and the FreeBSD derived OS. Or have pieces of Darwin been replaced by their GNU equivalents?
  • Using the ports system we are building our distribution quickly, and since it's Darwin, we can introduce many OSX users to free software in the process.

    I'm still not sure I get you. Perhaps all the Independence Day beer has gone to my head :-)

    I had assumed that Darwin was already a finished (although minimal) system. And coming from FreeBSD land, I had always envisioned the ports as being supplementary to the OS. Are you saying that GNU-Darwin is using the ports system to actually build the OS (as opposed to a buildworld)?
  • Sigh...

    The GNU System (notice the capitalization) is an operating system specifically described by RMS in the GNU Manifesto. It does not describe any Linux based system. A lot of the user environment of Linux is indeed based on GNU software, but that is insufficient to make it GNU.

    If Linus and friends had taken The GNU System and merely added the missing kernel, then yes, it should properly be referred to as a GNU based system. But that is not what happened.
  • The Apple Public Source License (APSL). This is not a free software license.

    There are problems with the APSL. However it still meets every definition of Free Software. RMS might not think it is, but the definition he created says it is.

    Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:

    The freedom to run the program, for any purpose (freedom 0).

    The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.

    The freedom to redistribute copies so you can help your neighbor (freedom 2).

    The freedom to improve the program, and release your improvements to the public, so that the whole community benefits. (freedom 3). Access to the source code is a precondition for this.


    The APSL meets every point. I'm not saying it's the best license out there. Far from it. But the APSL does manage to squeak through the definitions set in place by RMS decades before the creation of the APSL.
  • 1. APSL requires reporting to Apple.

    The four freedoms do not mention freedom from reporting modifications to the author.

    2. APSL does not respect privacy

    This is exactly the same as number 1. Again, the four freedoms do not mention freedom from reporting modifications to the author.

    3. Apple has too much revocation power under APSL.

    This flaw in the APSL was fixed. It had to be fixed before it could be officially Open Source. RMS even acknowledges that this problem is fixed.

    The only thing left in the APSL that is problematic to RMS (and to me as well, by the way) is the prohibition against private modifications used commercially. But again, the Free Software definition does not mention the freedom from reporting modifications to the author.
  • I didn't say he approved it. He said that the first two of the three objections he had to the APSL have been fixed by Apple. He still has an objection remaining, and that is the requirement to disclose all modifications. You can find this information in the very first paragraph of the page you site.
  • by Arandir ( 19206 ) on Wednesday July 04, 2001 @12:01PM (#108532) Homepage Journal
    I don't get this article at all. It's full of jargon, hyperbole and muddlethink. I'm sure there's a good idea buried in here somewhere, but I can't find it.

    These ports have tens of thousands of interconnections, called dependencies, which must be satisfied in order to build the applications.

    No port has tens of thousands of dependencies. And since you only build one port at a time, there is no need to take into account the dependencies of any unrelated port.

    Such a large and complex network of software dependencies...

    It's not a complex network. It's a simple tree.

    an uber-system has been superposed on the ports system

    Time to go back to English class!

    ...the naive user will not have to face a daunting tangle of dependency.

    A) Give your users respect. They are not naive. B) Dependencies are not tangled.

    Thus, the FreeBSD ports system, now as a cross-platform, globally distributed, cooperative development and distribution system could form a nexus of user freedom and empowerment.

    It's nice to read that on the 4th of July, but what the fsck does it mean?!?

    p.s. Why is he calling this version of Darwin "GNU-Darwin"? Is this a GNU project? Does he think that Darwin is really the GNU System?
  • Not at all! I said that every developer is different. By all means, do not do what I do!

    However, I can offer one solution. If you are releasing net-snmp for use on FreeBSD, I can only assume that you test it on FreeBSD, and thus have a FreeBSD box somewhere to use. Why not become the port maintainer yourself?
  • Maybe if he realised that rpm and apt are completely different things he would have a better time?

    apt uses rpm or preferably dpkg as a package management system. You use dpkg if something goes wrong on a debian system with packages.

    Happily, .debs rarely go wrong, as some care is usually taken in creating them. The same cannot
    be said of any rpm based system I have ever used.
  • Did you know that Dr. Evil is the princess of Canada?

    Yeah. Although he can't actually back that up with paper work.

  • Can't we just pay Dr. Evil six million dollars if he'll go away?
  • You don't understand the Ports system very well then. The source is fetched _automatically_ and then it's built _automatically_ as well. No knowledge of transfer protocols is necessary, no knowledge of autoconf, automake, configure, etc is necessary. All of the innumerable problems were taken care of by the Maintainer so that you don't have to worrya bout them. A single command does all that is required. Don't like or know how to use a command line? Click a button that does it for you. There are already a few GUI frontends to Ports. The OpenPackages project will definately be able to provide the framework for a userfriendly, custom installed-software-at-a-whim system.

    --
  • You gain nothing.

    If BSD developers were out to gain anything of material value they wouldn't be writing free software in the first place. This argument by GNU advocates is weak in this regard. If you're all worried about someone selling your code and you not getting anything in return, why do you write it? It's about writing damned good code for your own personal use. Most projects start out of the needs of the original author. So some big scary company comes and gets a copy... so what? Original Author keeps writing his code as it suits him and (hopefully) anyone else who finds it useful.

    WRT RedHat making money and OpenBSD and FreeBSD not.... *BSDs are software Projects, not software Companies. They're not OUT to make money. RedHat is. For that matter, Linux itself doesn't _make_ any money, and Linus didn't write it for that reason either. It got him a job and some nice free stock, but many companies who rely on the BSD projects hire full time BSD developers, so it works both ways.

    I think it's time you reevaluated your goals. What do you want out of the software you write? The respect and admiration of your peers or a wad of cash?

    --

  • Boy, that sure was a whole lot of well spoken points. I can't help but think they were meant for some other topic.

    I clearly wasn't suggesting or advocating writing open source software for free instead of writing commercial, closed source software for pay.

    If you don't want to write free (in both senses) software, then don't - and you won't here me, or ANY BSD advocate slight you for it. But if you do write free software, don't bitch about the money it's not making you. That's _all_ I said.

    --
  • It's not even worrying about making money, though money IS necessary...unless you are a trust fund baby with buttloads of mommy and daddy's money to suck off of. The problem is that you (the collective you) do all this work for the sake of BSD only for a company like M$ to come along, fold YOUR work into their product and use it to make tons of money with a system that is totally incompatible with yours. They use your work to try to create a world in which your chosen BSD is all but useless but to a few.

    My work is there, and it's still useful to anyone who used it in the first place. There's two scenarios here:

    1. My Software is the only thing of it's kind. I find it useful, which is why I wrote it, and others find it useful, so they chip in if and when they can. If they don't, oh well.
    2. My Software attracts the attention of Big Company. They copy (stealing is not possible unless they remove the hard drive from my CVS server) it, add some value (or not), and sell it as their own. Thousands of users who never heard of me or My Software now find Their Software useful. Their Software doesn't work with My Software. Big Company cashes in.

    Life for me and my copy of My Software is unchanged. So what if Their Software doesn't work with My Software? In Scenario #1 They don't even exist. The only difference is that Thousands benefit from My Software, where only a few did before. The terms of My License may or may not require that I be acknowledged for it.

    The Emphasis placed on your quoted text is my reponse to the bit about money. It (your argument) absolutely IS about money. (It's about something else too, which you either haven't realized or refuse to acknowledge - but I'll save it for later.) If it was money I was interested in I would have either made it closed source in the first place, or look, it's a BSD license, so I CAN!

    I also assume that the incompatible software you're referring to is Kerberos. If this is the case then you misunderstand the Kerberos issue. Please search for my nick among the (now flattened) comments on this older /. story [slashdot.org]. (There is either a feature or a bug that is preventing me from linking to the specific ${cid}s. Probably related to the flattening.)

    The bigger problem is that the BSD license selects for fragmentation rather than cohesiveness. Apple takes BSD, folds it into their OS, software developers write programs to work with Apple's BSD - none of it will run on your personal BSD. Your hard work was used to create a system that doesn't support your chosen OS. You are left out in the cold vis a vis software developers (no games or any other possibly desirous apps for you - just whatever you and your relatively few buddies can spin up in a weekend).

    I think you're confused about a great many things regarding BSD and MacOS X. BSD hasn't been folded into MacOS. MacOS has been re-written on top of Darwin, which is Mach/FreeBSD. Any MacOS developers would be writing for MacOS. This means (IIRC) Carbon and Cocoa software, things which aren't possible on a vanilla BSD system anyway.

    Darwin developers on the other hand, whether their dev OS is MacOS X or Darwin on PPC or x86 would be writing for the Unix OS that Darwin is. Any (non arch dependant) code would run with little modification (assuming it was OSS) on any *nix.

    Me and my buddies were there before, and we'll be there after.

    This may be perfectly fine for a few hardcore BSD users but it is NOT in the best interests of standards and general end-users.

    Evil Mind Controlling Mega-Corps aside, how is the widespread use of my code not a benefit to others? As you say, they are subject to the whims of Evil Mega-Corp. They always will be whether I write BSD software or not. If this bit is an argument in favor of the GPL, I'm not seeing it. The sheep will use what the Evil Mega-Corp tells them they should use, be it _in spite_ of the GPL or _because_ of BSD.

    I'm afraid I lost you on the next paragraph. Definate degradation detected.

    M$ CAN and WILL embrace, extend, extinguish ANYONE who tries to compete against them, whether they are offereng some BSD variant or not. On the other hand, M$ cannot legally do this to linux. They cannot embrace and extend it, thus marginalizing it - if they tried, they would be de facto violating copyright law and would be liable.

    Microsoft certainly could(we're talking possibility here, not probability) compete against and extinguish Linux. There's nothing illegal there. They can even embrace it. And they can even extend it. Only if they don't give those extensions back is it a violation of law. It's never going to happen of course, but for the purposes of this debate, it's not only _possible_, it's legal. I'm afraid you left yourself open with that "or not".

    I really don't see how *BSD and its licensing is in any way an improvement on anything. It still allows monopolists like M$ to do business as usual whether they use BSD stuff or not.

    The contradiction there is so strong it's almost painful. BSD and it's license allows monopolists to continue even if they don't use it? Come again?

    Now for the something else. It's about control. That's it. It's not about money, though that's the first thing out of everyone's mouth. It's not even about Freedom (both kinds).

    Is the GPL a good thing? Yes. Are Berkeley style licenses a good thing? Yes. Is one better than the other (The improvement you suggested)? Depends on the software.

    Dramatic finale omitted.

    --

  • I was directly responding to your assertion that the end user has to know how to fetch, configure, build and install software.

    They do not. Not with *BSD Ports or Packages or any of the Linux package systems.

    Whether just running 'make' is a significant difference over './configure && make install' isn't the point. It's that the user doesn't have to know how, which you claimed they did.


    --
  • >>some undocumented APIs gave a "massive advantage" to the "Office Suite".
    Simple test. Crash machine on every call to an undocumented API. Will Microsoft Office still run?

    >>The Windows NT kernel is undocumented for a reason ... There should be no need to call it directly.
    Errr, what else should an application program call for kernel services? I think on any viable system, the kernel tends to be extremely well documented.

    There are enough known undocumented APIs and enough history that it is inconcievable that Microsoft is not using them to give a "massive advantage" to the "Office Suite".

  • The "massive advantage" is not from one undocumented API, but from many undocumented APIs. This includes lack of documentation of any parameter values.

    >>An application ... calls an intermediate personality layer.
    Repeat three times with a straight face.
  • The thing that makes Java WORA is the fact that the API goes with the language and the runtime enviroment.

    Java isn't WORA in general - or rather, when it is, it works badly.

    But that's besides the point.

    Java being WORA and C# being 'not-WORA' doesn't have ANYTHING to do with C# being cross-platform.

    Cross Platform != WORA. Get that through your head.

    Simon
  • Who's the one picking a fight here?

    You guys started it. Microsoft finally noticed that not a day has gone by since 1996 (or earlier) without some zealot calling repeatedly for Bill Gates' head on a platter.

    So after all that namecalling, threats to throw grenades at the Redmond campus (I remember reading THAT one in 1998, and nearly called the FBI)... what do you expect?

    You think this is *bad*? What if they lowered themselves to the average Slashdot poster's level? Wouldn't that be scary...

    Si
  • by AtariDatacenter ( 31657 ) on Wednesday July 04, 2001 @08:29AM (#108546)
    This is going to sound trollish, so let me apologize in advance.

    I guess I'm not up-to-snuff in my BSDisms. What is this ports facility, and what does it have to do with .NET? I read the article and was even more confused. I see it has something to do with package dependancies, but that's about it.

    Can someone spare me a clue?
  • Yes, but my point is that people don't do that. (which is why something slightly more automatted is needed).
  • Don't get me wrong... The portst tree is an excellent thing (as are .deps, .rpms, ...). My only complaint is about local modifications to sources that have no reasons for being kept solely there. (note that there are cases where you would want to keep a patch away from the developers, like if you wanted to release the patch under the GPL and the original code was BSD based. Giving them the patch would destroy their licence).
  • by hardaker ( 32597 ) on Wednesday July 04, 2001 @10:33AM (#108549) Homepage
    There are serious problems with porting trees that need to be addressed by their maintainers (but frequently aren't). Specifically, patches that go into ports trees or are applied to binary releases are rarely given back to the developers of the original package. I've been distributing the net-snmp (was ucd-snmp) [net-snmp.org] toolkit for years now and nothing infuriates me more than running across a patch I haven't seen before being applied to some distributions private code cache.

    By far, the worst distributor in this regcard is RedHat. I figured for years they were merely building the source and distributing the binaries as is. The first time I looked at the spec file I found around 4 patches I had never seen before and didn't even know some of the bugs existed. Well, I thought, I'll contact them and see whats up. "Sorry, I'll try to make sure patches get your way in the future". Of course, when I checked the source rpm for the next release I found yet more patches I'd never seen... Sigh... I don't have a solution to this problem, though an obvious one might be something along the lines of at least asking the maintainer if they wished to receive CVS messages or CVS patches on a regular basis from the ports trees, or to be added as a default contact for the external bug database for a given package (To solve the redhat problem, I'm forced to go search through their bug database occasionally). Don't get me wrong, I think distributing the source and binaries in an external "easy-to-use" fashion is a great thing. What I consider wrong is to not at least mention to the original developers that changes have been made. Sure, its legal and even goes along with the licence in most cases, but in the long run I would think it would save the ports maintainers a lot of conflict merging if they kept in touch with the package developers.

  • by hardaker ( 32597 ) on Wednesday July 04, 2001 @12:22PM (#108550) Homepage
    • Case in point: net-snmp on FreeBSD-4.3. The majority of patches are to makefiles. The majority of the rest only updated the FreeBSD version macros. Actual code changes are rare, and are only for the purpose of getting the software to build.

    But see, you missed the point. We try to release the net-snmp software for use on FreeBSD so why wouldn't I want to see even those makefile patches so I can try to solve your problems in the main distribution? What if people don't use the ports tree and download the real release? What if they want the most recent CVS code from our cvs server?

    Following your example, should I go remove all the freebsd specific code from the net-snmp distribution because the proper place for it is in the ports tree since no one else but freebsd folk will need it?

  • http://rpmfind.net
  • First BSD version: 1BSD (march 9th 1978)

    see The Unix history [wanadoo.fr] page for detailed information about all Unices.
  • the ports system... installs all add-ons in /usr/local

    Yuck! /usr/local is for LOCAL software. Not managed ports stuff. I'd like to see something like /usr/ports for that stuff.


    --

  • This is assuming FreeBSD cares aboutthe average windows user. From my own expeience and what i've encountered FreeBSD cares about being the best it can period. World Domination is not a past time for it.
  • I'm not saying that the ports is an all encompassing
    substitute for .NET, but rather, I see some development potential where
    the ports system might stand in for .NET-style service applications, but
    free. I don't want to use Word for the rest of my life, and I
    especially don't want to pay subscription fees for it. I see M$ trying
    to kill free software with .NET, and we need a response. I'm arguing
    that the ports could be a crucial part of that response, which could
    render .NET valueless.

    A response is better than carping about M$, or cowtowing with open source support for an initiative that could potentially damage the free software movement.

    Regards,
    proclus
  • From the GNU-Darwin masthead:

    GNU-Darwin aims to be the most free Darwin-based Unix distribution. Our mission is two-fold: Focus on new projects that leverage the unique capabilities of Darwin/Mach and help Apple users to enjoy the benefits of free software.
  • Thank you for this helpful criticism, and in the next paper, I will modify the presentation accordingly.

    Regards,
    proclus
  • The Distribution has ported free software to Darwin in order to build a stand alone Unix distribution, and at the same time, to expose Apple users to free software. GNU-Darwin is free software running on Darwin. Mac OSX is proprietary software running on the very same Darwin. All of the GNU-Darwin offering run unmodified on Mac OSX.

    Although APSL is OSI approved, and Darwin is undeniably open source, it is not yet truly free. The Distribution is unsatisfied with the current state of the APSL, and we are advocating to FREE Darwin according to the FSF definition.

    Regards,
    proclus
  • > However it still meets every definition of Free Software.

    APSL is not a free software licence.

    1. APSL requires reporting to Apple.
    2. APSL does not respect privacy
    3. Apple has too much revocation power under APSL.

    http://www.fsf.org/philosophy/apsl.html

    For these reasons, The GNU-Darwin Distribution has not made any contributions to APSL covered code, and we are advocating for greater freedom.

    Regards,
    proclus
  • GNU-Darwin is Darwin itself, but overlayed with free software. Mac OSX is Darwin itself, but overlayed with a proprietary interface. We are using the ports system to bring free software to the platform as quickly as possible.

    Now that we have all of this free software for Darwin, you can use GNU-Darwin as a stand-alone Unix distribution without Apple's proprietary parts. Most interestingly, all of our contributions are 100% compatible with MacOSX.

    Regards,
    proclus
  • Nope these three problems have not been fixed. APSL is OSI approved, but it is not a free software license. You say that RMS approves of APSL now, but that is incorrect. Read the FSF website.

    http://www.fsf.org/philosophy/apsl.html

    Regards,
    proclus
  • My apologies, that last post of mine lacked a little in accuracy, but the fact remains that Darwin is not free software until this problem with the APSL is fixed.

    BTW, I have really enjoyed our discussion here. Thank you for your excellent questions, Arandir.

    Regards,
    proclus
  • It appears that you are speaking as someone who is satisfied with a finished distribution. In that situation, you might scan the ports for software that you would be interested in and build those individual ports. That's fine, and that is our goal with the ports system, but at present, we are doing something quite different from that.

    We are building a new distribution. We want every single port to build as soon as possible. That means modifying and optimizing the ports system towards a new purpose. We must consider the ports as a whole and take into account all of the dependencies of all the ports together.

    Using the ports system we are building our distribution quickly, and since it's Darwin, we can introduce many OSX users to free software in the process.

    There is no "muddlethink" involved here. We are moving from virtually zero free software availability for Apple users to 100%. We are not using the ports for selectively getting the software we want, but rather, we are using it to bring a whole world of software to a new platform. Since the ports is a distributed system, we have a de facto world of collaborators.

    It is no leap to see how this frees users in contrast to .NET, which would have nothing to do with free software.

    Regards,
    proclus
  • by Platinum Dragon ( 34829 ) on Wednesday July 04, 2001 @09:57AM (#108573) Journal
    All the more power to them, however the community should focus on creating, and making things better, not trying to pick fights

    Hallowe'en Documents.

    "Linux is like Communism"

    "The GPL will steal all of your hard-earned IP."

    "The GPL is like Pac-man."

    "We're going to support FreeBSD but not Linux because the license is better...for developers. Really."

    Who's the one picking a fight here?

    ...hasn't anyone ever thought that there are Windows programmers who develop things on their own, post them at sites like Tucows, and are actually happy with using Windows.

    Oh, I know there are people perfectly happy with using and developing on Windows. I don't wish to deny them that choice. The problem is, Microsoft wishes to deny me the choice to use anything else, by making sure Microsoft "standards" are more prevalent than any other "standards", real or perceived, and ensuring you can only take advantage of MS "standards" on MS platforms. Individual actions alone may not be "smoking guns," but the sum of their actions and behaviour towards any potential competitors and developers leads me to believe they wish to deny me and millions of others a choice we don't begrudge their customers.

    That is wrong. I don't mind them innovating. I do mind them assimilating and trying to make sure the only way is the Microsoft way. I'm a consumer too, and I demand a choice of software and available tools, even if MS wishes to deny me one.

    Call it paranoia, but that's the view from here.

  • The FreeBSD porters handbook says:
    15.20. Feedback

    Do send applicable changes/patches to the original author/maintainer for inclusion in next release of the code. This will only make your job that much easier for the next release.

  • by glitch! ( 57276 ) on Wednesday July 04, 2001 @08:43AM (#108576)
    Every time Dr. Evil announces that he is working on a new weapon, you folks always assume it is
    going to be some orbiting death-ray, a volcano machine, or a bomb that will blow the earth into
    little bits. You are always jumping to conclusions...

    Maybe this time Dr. Evil is making a weapon that will fight crime and make our streets safe. Or
    one that only works against crooked lawyers and politicians. But I repeat myself. Did you even
    consider the possibility that Dr. Evil might be trying to be helpful this time? No, you didn't.

    Frankly, if I were Dr. Evil, I would be pretty upset with this constant stereotyping. Maybe that
    is the cause of his inner anger that causes him to do these things. You are to blame, not him...
  • He he. I'm posting this from a Gentoo-RC5 box as we speak It really is pretty cool. Still needs a bit of polishing up, but when its ready, I can guarentee that this distro is going places! PS> It has i686 optimizations!
  • by Colm@TCD ( 61960 ) on Wednesday July 04, 2001 @09:29AM (#108581) Homepage
    I used to agree with you, until I got into Debian. Apt truly rules! This isn't partisan (well, okay, it is, but it's for very good, objective reasons). The Debian Apt system is really, honestly, the best software-getter I've ever seen. In conjunction with the Debian Packaging Guidelines, which cover many very important rules for the creation of Debian packages (basically, that it should follow certain well-defined procedures regarding libraries, configuration requirements, file locations etc), Apt really spoils the sysadmin. It would be very painful for me to move to anything other than Debian now...
  • The problem is, Microsoft wishes to deny me the choice to use anything else, by making sure Microsoft "standards" are more prevalent than any other "standards", real or perceived, and ensuring
    you can only take advantage of MS "standards" on MS platforms. Individual actions alone may not be
    "smoking guns," but the sum of their actions and behaviour towards any potential competitors and
    developers leads me to believe they wish to deny me and millions of others a choice we don't begrudge their customers.

    That is wrong.


    Think to yourself about what you've just summed up for the rest of those who would want to argue your points: Microsoft wishes to deny me the choice to use anything else Microsoft may wish to deny you a choice, if they decided today taht anything MS compatible HAD TO use ONLY MS based products you know what, they're only trying to deny you a choice, of which you could easily move away from Microsoft.

    Doesn't that seem more logical than to always tread along the same thought of an evil corporation "assimilating" everything in site? Move away, go find another OS, show MS that by you using another OS they mean little to you. Isn't that sweeter justice than moaning and groaning about something out of your reach (MS' so called monopolization)?

    By constantly playing into the same "MS is evil", "MS is assimilating", "MS must die", or any other form of thinking along those terms, you're no better than they are. However as someone who has moved away from their (MS') products, you can show that their is life aside from MS, and by contributing positively without all the name calling, finger pointing tactics, people will take a closer look to why others have move away from MS.

    It's a nice project to have the FreeBSD ports universally available to other nix variant users, but the comment does little more than annoy. Instead of focusing such negative vibes, people should try to simmer down, and make positive moves under the nix community. Make standards, improve on existing ones, instead of waisting time with the childish games.

    My two cents on it all
  • by joq ( 63625 ) on Wednesday July 04, 2001 @08:32AM (#108583) Homepage Journal
    What possible significance could .NET have in such a world, where thousands of free software applications can be readily downloaded and configured especially for you, especially for a computer that is optimized according to your own personal needs and desires and none other? This
    is the world where the user operates the distribution building tools, and we now have all of the components at hand, which are required to make this world real.


    It's instances like this which will push MS over Unix in the end. " we now have all of the components at hand, which are required to make this world real. " For business that have been using MS based products for years, many have made money using Windows so why would they want to switch when people keep up with the name calling and finger pointing? (re: GPL arguments vs. MS and vice versa)
    This week, Microsoft announced that it will work with Corel to port the .NET Common Language Infrastructure and the C# programming language to open-source OS FreeBSD, a Linux competitor. Microsoft submitted the Common Language Infrastructure and C# to the ECMA standards body last October, and the company says that the FreeBSD implementation will be the first on a platform other than Windows. The company believes these tools will be used for academic, research, debugging, and learning purposes on FreeBSD.
    For a company so evil, at least they're extending a hand, but according to some this is viewed as MS looking to stir up troubles in the open source community. Maybe so, but how is this comment any different from stirring up the same type of bias "What possible significance could .NET have in such a world, where thousands of free software applications can be readily downloaded and configured especially for you" hasn't anyone ever thought that there are Windows programmers who develop things on their own, post them at sites like Tucows, and are actually happy with using Windows.

    All the more power to them, however the community should focus on creating, and making things better, not trying to pick fights. I used FreeBSD at home and Open for my server, and have a laptop with W2K that hasn't been used in eons, and each serve their own purpose, bottom line. Comments and write ups so biased to little to sway my vote of confidence in any OS just because someone claims it to be so much better. No sirs I'll be the judge of that as will most others, so why waste time beating a dead horse. It's these same comments used against the open source community.

    Everyone wants to jump in on the action, and post why they're better, and oh by the way here are 30,000 more free programs. Yes 30,000 more free programs, 30,000 more comments, and now the whole concept is lost isn't it. Meanwhile MS stands out because they focus. So please focus on making things better not worse with such biasedness
  • It does none of these, clearly. In that sense it is not a competitor to .NET at all. The article is misleading in that sense.

    It is more of a competitor to MS's vision of subscription-based services (e.g. Passport) and software leases. These form another part of .NET.

    In fact the closeset analogy in MS-land is Windows update.
  • by Jace of Fuse! ( 72042 ) on Wednesday July 04, 2001 @11:37AM (#108585) Homepage
    There's nothing like reading about an application out there and wondering if its in the ports collection.

    I had never tried GAIM, and wasn't sure it was available for BSD. But wow.. there it was in the ports...

    make
    make install

    Groovy. Now I have GAIM. I can really dig this whole PORTS thing. :)

    "Everything you know is wrong. (And stupid.)"
  • No, the port will get an old version, it gets exactly the version it needs. Should the original site no longer have the older version, all original tarballs are cached on ftp.freebsd.org, which is used as a fallback to get the tarball from.

    All ports are stable, there are no development versions of ports. This is possible since FreeBSD ports (unlike Debians apt) only cover add-ons to the operating system. The base operating system (including userland and kernel) is not built together of all little ports, but is one entity. The advantage is that any FreeBSD installation can expect to have at least a similar base everywhere (unlike Linux distros, that tend to be composed of zillions of small packages many of which are optional to install).

    Trojan horses are no issue, since all source files are protected with an MD5 checksum (that is, the port includes the MD5 checksum of each source file, and checks them on downloading).

  • by Baki ( 72515 ) on Thursday July 05, 2001 @02:49AM (#108587)
    One of the nice things of the ports system is that it installs all add-ons in /usr/local, not in the standard /usr/lib, /usr/bin and /bin directories. I hate my bare standard operating system being filled with garbage of add-on or optional products. No UNIX does that, except for Linux.

    Further it encourages source instead of binary based distribution, still makes using the sources just as easy as using binary distributions for other package systems. The advantages of that are:

    • Less chance for virii or trojan horses
    • Often smaller files to be sent
    • Updates to the package/port itself, not to the original application, only need tiny diffs to be sent.
    Another plus (which it shared with debians apt) is automatic dependancies. A port that needs other ports/libraries will automatically get and install those as needed, you don't need to think about prerequisites as with rpm.
  • FreeBSD is not a linux distro, not everyone can post changes into the system, only commiters.

    Ports depends on someone figuring out how to compile various packages on new systems - no centralized point of authority (or, more importantly, blame).

    At least with the FreeBSD ports it is very easy to find who has commited the port and get them to fix it or get help. It very much DOES have a central authority.

    If you haven't checked it out, see what ports [freebsd.org] really is... who knows, you may like it ;-) Also, check out the manual pages [freebsd.org].
  • p.s. Why is he calling this version of Darwin "GNU-Darwin"? Is this a GNU project? Does he think that Darwin is really the GNU System?

    Check out http://gnu-darwin.sourceforge.net/ [sourceforge.net]. It's Darwin plus all the GNU stuff. They initially had problems getting applications so they decided to include FreeBSD's ports tree. It has worked wonderfully for them.

  • No clue. Those GNU operating systems don't have good documentation. It may or may not, these days, but since they don't document it very well, (an artifact of not having any historical perspective, which has evolved out of their lack of source code control), it's not worth it for me to go digging in their archives for what they've been doing since last Tuesday.

    But after a quick glance it appears to be Darwin+GNU bits+FreeBSD Ports.

  • from www.gentoo.org [gentoo.org]

    "Gentoo Linux is a fast and modern, completely free x86-based Linux distribution with a clean and flexible design. Unlike other distros, Gentoo Linux has an advanced package management system called Portage. Portage is a true ports system in the tradition of BSD ports, but is Python-based and sports a number of advanced features including dependencies, fine-grained package management, "fake" (OpenBSD-style) installs, safe unmerging, system profiles, virtual packages, config file management, and more."
  • by blakestah ( 91866 ) <blakestah@gmail.com> on Wednesday July 04, 2001 @06:37PM (#108597) Homepage
    What's wrong with grabbing a source package and doing rpm --rebuild? Okay, that's two steps instead of one, but it's not that much of a big deal.

    Well, first you have to FIND the package. Then you can download it. Then build it.

    Ports and apt-get (Debian) use standard distro archives. You never need to FIND the package. This may seem like a little step improvement, but it leads to a HUGE increase in user-friendliness.

    As for apt vs ports - both are great and both work well. Competition is good. One can expect each of them to pull other free unices up to their level in the next two years. And that is good for everyone.
  • by blakestah ( 91866 ) <blakestah@gmail.com> on Wednesday July 04, 2001 @08:29AM (#108598) Homepage
    Ports: suck source and dependent source down across the net, configure for your system, build, install.

    Apt-get for Debian: suck binaries down across the net, resolve dependencies, install

    All other distros: trying to catch up.

    Ports is even a step more fine grained than apt-get, simply because it works with source, and incompatibilities are nearly impossible (the package will refuse to build instead).
  • The Ports system is great, sure beats the hell out of RPM and the like. But comparing Ports to .Net is an apples and oranges comparision. What does a source code retrieval/build system have to do with a multi-platform runtime engine for applications. Comparing Java and .Net is closer, but .Net will support (MS claims) fifty languages not one. All .Net really is, is a way to get COM on more platforms.
  • Wouldn't it be possible for the kernel developers to add Linux support for FreeBSD binaries if it hasn't been already and then just install the .NET tools under Linux?

  • By your reasoning (a bit stretched IMO), we have already a .NET-like platform : it is called autoconf+automake :-).

    Kidding aside, they are what I call 'the hard way to portability', and have managed to port hundreds of software packages on several Unix platform (and now they are slowly but constantly creeping on the 'enemy' platform, too ).

    Pity that most developers are lazy(including myself) and wants more easier way to write portable software, like Java or other byte-compiled languages.

  • The vision of .NET doing all sorts of RPC with XML over HTTP as the protocol to access web services (e.g. obtaining the current headlines on slashdot, stock quotes, perform a translation, or some other interesting web service), the author of the original article may have been trying to say that having access to the multitude of Open Source applications out there makes web services redundant since you could just download an Open Source app to do what the web service does.

    This is probably true for a subset of web services but things like a realtime flight tracker provided by the airline's website, UPS's package tracker, real time stock quotes, or other information that belongs to a company that you cannot directly access is where web services will shine and simply downloading Open Source apps or various screen scrapers won't cut it.

    PS: I posted part of this comment in another thread.

    --
  • by Carnage4Life ( 106069 ) on Wednesday July 04, 2001 @11:04AM (#108606) Homepage Journal
    I suspect that you didn't read the article at all. Your comments have nothing to do with the article which in turn had nothing to do with .NET. Here's the quote from the article that mentions .NET.
    Thus, the FreeBSD ports system, now as a cross-platform, globally distributed, cooperative development and distribution system could form a nexus of user freedom and empowerment. What possible significance could .NET have in such a world, where thousands of free software applications can be readily downloaded and configured especially for you, especially for a computer that is optimized according to your own personal needs and desires and none other?
    This somehow implies that being able to quickly download and Open Source applications is somehow in competition with .NET which is about XML web services [xml.com]. It is a thing of particular bemusement to me that Open Source advocates and Slashdot editors keep attacking a .NET which is a figment of their imaginations and has nothing to do with what truly constitutes .NET (which can be gleaned from just reading the .NET website [microsoft.com]).

    On second thought there is one way one might consider that this competes with .NET. The vision of .NET doing all sorts of RPC with XML over HTTP as the protocol to access web services (e.g. obtaining the current headlines on slashdot, stock quotes, perform a translation, or some other interesting web service [xmethods.com]), the author of the original article may have been trying to say that having access to the multitude of Open Source applications out there makes web services redundant since you could just download an Open Source app to do what the web service does. This is probably true for a subset of web services but things like a realtime flight tracker provided by the airline's website, UPS's package tracker, real time stock quotes, or other information that belongs to a company that you cannot directly access is where web services will shine and simply downloading Open Source apps or various screen scrapers won't cut it.

    --
  • try this book :
    The Microsoft File by Wendy Goldman Rohm
    or this one
    Undocumented Windows by A Schulman [accu.org]
    or this one
    Unauthorized Windows 95 by Andrew Schulman [accu.org]

    or this one :

    Undocumented Windows NT, by Prasad Dabak, Sandeep Phadke, and Milind Borate
    example chapter [sonic.net]

    Here's a whole bookstore making money from undocumented Windows API calls :
    http://www.sonic.net/~undoc/bookstore.html [sonic.net]

    what something online?

    try here http://www.vbworld.com/api/shelldoc/ [vbworld.com]

    a password cracking utility that uses Win32 undocumented api calls to display the currently logged user's password [password-crackers.com]

    API: Access/Office and AddressOf Operator [mvps.org]

    some more software [lastbit.com]

    is that enough yet ?


    .oO0Oo.
  • by pi_rules ( 123171 ) on Thursday July 05, 2001 @04:52AM (#108615)
    I think I get what the writers of the article were getting at.

    Why use .NET (which lets people not worry about having the newest software installed on their system) when you can just use something like ports and keep the software on your system?

    Windows users are sick of .DLL hell and having to upgrade software because of bugs and such. .NET will let them keep all logic off their computer and only keep the "fluffy" presentation layer stored locally. It's a good idea.

    But not very practical -- with ports (and Debian's apt) it's easy to keep everything up to date and in perfect working order without any real clue as to what's going on.
  • Strap on your virus checker before trying some of these links.
  • by Lord Omlette ( 124579 ) on Wednesday July 04, 2001 @08:34AM (#108620) Homepage
    Hello. Could one of you PLEASEPLEASEPLEASE explain to me what this is and how it goes against Microsoft's .NET? Thank you.

    If you get a chance, could you explain:

    -how does it make it easier for systems to communicate with each other? (soap stuff)
    -how does this make it easier for people working in multiple langauges to integrate their stuff? (you know, people in vb inheriting classes from c++, people in delphi using source written in c#, etc)
    -how does this make it easier to write ASP applications that don't care what browser you're using? (webforms)

    Major thanks in advance

    Peace,
    Amit
    ICQ 77863057
  • I don't know if ports is the answer, but the spirit of 'we don't have to do what MS does, we can do better' is a little weak on the free side sometimes.

    If a suitable competitor of .NET can be developed on the free side, then migrated over to WINdos, that would be a huge victory for freedom.


    Treatment, not tyranny. End the drug war and free our American POWs.
  • by small_dick ( 127697 ) on Wednesday July 04, 2001 @10:37AM (#108623)
    First off, MS never 'extends a hand' to anyone. They are merely offering a subset of the service so as to appear 'cross platform'.

    Just like everything they do, it's all about 'embrace, extend, extinguish'. Whatever bones they throw to the free side, it will always lag behind, and be feature poor, compared to their flagship.

    This attempt to take over the server side authentication process may succeed, but it may fail...just because companies don't want to be a slave to MS.

    It's impossible to make the argument that MS has ever done anything to 'help' their users...but they continue to try and find ways to extract as much money as possible from their user's pocketbooks. Server side authentication and proprietary services will kill all competitors, and remove all choice...earning MS a fortune that will make their current trasure chest seem like a pittance. Do we want to pay for that?

    When 'free software' beats the final criticism into the ground -- that it is difficult to install and expensive to administer and maintain -- MS could start to lose miserably.

    Developers have got to start makeing their user schemas intuitive and logical, and that takes user testing...I think we are seeing a lot more of this, and it is on the increase.


    Treatment, not tyranny. End the drug war and free our American POWs.
  • by marm ( 144733 ) on Thursday July 05, 2001 @05:10AM (#108627)

    Ports depends on someone figuring out how to compile various packages on new systems - no centralized point of authority (or, more importantly, blame). Furthermore, there's no equivalent of a device-independent language for writing new applications.

    Are the moderators on crack today or is this your troll account that you then mod up from your normal account when you have mod points?

    Don't be ridiculous. The centralized point of authority for the BSD ports system is the BSD ports team. In exactly the same way as the Debian developers (and bug-tracking system) are your first port of call for problems with Debian-packaged software. Of course you can't really sue them if something terrible happens, but you can't sue Microsoft either - check out your EULA.

    As for there being no device-independent language for use with the ports system, what do you think Java is? Or, for that matter - Perl and the Bourne Shell, which are almost universal throughout the Unix world? Sure, Perl is interpreted (although it doesn't have to be) but even as an interepreted language it shifts very quickly. Don't forget things like the GTK+/Perl bindings too, so don't argue you can't write user-friendly GUI apps with it - you can.

    What would be an interesting project though is a JIT compiler for Perl - it has everything going for it otherwise as another, Open Source alternative to C#, including huge ease of use advantages.

  • by andr0meda ( 167375 ) on Wednesday July 04, 2001 @02:13PM (#108628) Journal

    Well some people are really into the .NET cloning idea, but for starters I don't think .NET will actually work for the desktop market, because of one very simple reason: bandwidth. The internet is simply not ready for service based applications. And certainly not for dbase intense applications that store the contents of your letters or documents.

    .Net is all shiny and beautifull technology, and the concept of downloading the equivalent of dlls instead of jars must sound like Stravinski to Gates, but the hard cold truth is that it will atleast take 4 to 5 years before the world is done with struggling over bandwidth (if at all).

    There's also another reason why I wouldn't recommend cloning .NET on linux. Many people allready suggested that keeping a clone up to date with microsoft's original is firstly a sign of weekness in the creative department, but more importantly it is sensitive to changes in the core, so that a clone will never be trustworthy (and thus market degraded). Businesses will never ever want a linux platform for running .NET. Thirdly, if MS should on the contrary decide to let linux clones thrive and florish, who will benefit from that ? The company that sells the services, because they have a cheapo .NET client and everything works as expected. Right. Now remember the Kodak story from a few posts back and you'll know that MS is not going to let this happen.

    In short, I think if MS manages to get control over 3rd party services in some way, linux should not design .NET because it will be like a poisoned apple, a virus, allowing only more desktops to run native MS code (that gets things done, no hard feelings). If MS doesn't manage that level of control, then obviously they will break the clones by changing the platform specs, rendering linux desktops unusable in the business world.

    Quite a dilemma. Ofcours the OpenSource movement could try to write it's own alternative platform now, in fact, it should be doable with such fine examples like c# and java, not to mention other languages which may be even more runtime-optimizeable and memorymanageable. On the other hand it is also worth noting that SUN has developed Jiro, Jxta and ofcourse Jini and JavaSpaces, which all focus on making J2EE a reality as a service solution. So in fact .NET, which is not funcitonal right now, allready exists, only under a few different API names. Maybe it's not a stuned as you would like, but hey, don't expect .NET being perfectly tuned and ready for another 2 years minimum.

    Anyway, I've never really understood why the linux community would rather bash MS and run w2K alongside instead of opening their eyes and see SUN really doing a tremendous effort to take away a bit of the MS heat. Sure, Java may not be as sexy as your python, perl or c, but it the Grand Scheme of Things(tm), it is the best alternative anyone can imagine. They have bug submission, they have structures set-up to work swith large userbases, and they do deliver, allthough not OpenSource. I don't see anybody developing what SUN has done AND succeeding to outrun MS with OpenSource initiatives just yet. It's a painfull truth, but we should not kid ourselves and make sensible choices nonetheless.

    Cheers,
    Ignace
  • Darwin Installation Manuals for both the Intel and PPC platform can be found at http://www.futureunix.net/darwin/ [futureunix.net] - soon to be available from Apple. Your feedback is encouraged so if you get Darwin up and running and have some ideas or tips to contribute to the documentation. Let us know!

    -Pat

  • You are right to be confused. I know the ports system like the back of my hand, and I can tell you it has nothing to do with .NET whatsoever. Move along now, nothing to see here.
  • What does this have to do with .NET; I assumed there would be some kind of intermediate code base or something. But all I see is an open platform.
  • It's nice that it runs on MacOS and a variety of unices, but where's the Windows version? The world does not revolve around unix anymore, and if you expect this to make even a small dent in .NET usage, then it HAS to run on Windows. If it doesn't then you might as well quit now.
  • by Zenin ( 266666 ) on Wednesday July 04, 2001 @01:10PM (#108657) Homepage
    By the way, BSD didn't exist in a Free form until after Linux was already started.

    Yes and no. It did exist in "free form", then it got attacked by AT&T (for trying to be "free") and was in limbo until the courts and coders pulled the last bits of AT&T code out and created 4.4BSD Lite. Had this useless exchange never happened, it's very unlikely that Linux would have existed at all. -At least according to interviews I've read of Linus, stating how he'd probably have just used FreeBSD for study way back when...if it hadn't been encombered.

    On other notes...
    BSD didn't invent TCP/IP, but it did give Unix it's first incarnation through the Berkeley Sockets interface. First VM in a Unix system was also BSD. Reliable signals, BSD again. Fast File System, BSD. Passing descriptors over UDP, BSD.

    Not that SysV just stood there. Most all ideas from BSD have been adopted by SysV, as well as many the other way (shared memory, streams, etc).

    A HUGE part of what all Unix is today is directly traced to BSD work. Work from Linux so far, hasn't shown really up anywhere else. Don't get me wrong, Linux is a great system...but innovative it isn't. Thankfully, one doesn't need to innovate to be useful. -Hell, if that was the case Unix itself would be long since dead. :-)
  • Yes - Gnu/open group/AT&T/Xerox/Motorola/Trolltech/......../Alan Cox/Linus/Linux, or perhaps just Linux-PPC.

    The linux kernel was developed with the use of gnu tools, but the "gnu" prefix to linux is a recent thing and not added by a developer of linux anyway.

    I'd better get back to work using GNU/NT4 (the cygwin tools are the most commonly used user programs on this machine).
  • by Tipsy McStagger ( 312800 ) on Wednesday July 04, 2001 @08:43AM (#108661)
    Dosen't apt-get install source xxxxx suck in the source, compile and install?
  • by BastardOpFromHell ( 452398 ) on Wednesday July 04, 2001 @08:25AM (#108666)
    I love the FreeBSD ports system. To me, it alone is reason enough to run FreeBSD (though I run Linux). I'm glad to see it coming over to Linux systems!

    If you haven't tried the ports system, I highly recommend you do so. They're a VERY convenient way to install new software.

  • "as a good antidote for .Net and other subscription-based systems."

    I'm sure I'm not the first person to ask this: "what's wrong with them?" Simply because they're run by Microsoft? Nice excuse, but, I usually need something a bit more substantial...

With your bare hands?!?

Working...