Slashdot Mirror


FreeBSD Ports for GNU/Linux

proclus writes: "GNU-Darwin has provided a special FreeBSD ports tarball (20 Mb) for GNU/Linux users. We have modified the FreeBSD Ports System to bring thousands of free software offerings within the reach of every GNU/Linux user. The system is not fully automated yet, but you can untar it in your home directory and try it. Just follow these directions. This system provides full access to the FreeBSD ports, so that users can compile and install software in their home directories. Root access is not required."

294 comments

  1. Just get it over with by Anonymous Coward · · Score: 0

    Install FreeBSD if that's what you want.

    Forget GNU. Forget Linux. Forget BSD. Forget Microsoft.

    Just use the system that best fits your needs. This may mean that your pet OS is not a universal fit for someone else.

    1. Re:Just get it over with by esper_child · · Score: 1

      This is a good thing beleive it or not. It should mean that program files will be compatable across systems. Porting software to a bunch of different operating systems is a good way to get near perfect compatability between multiple different operating systems. This should in theory make a network work a little bit smoother for the user who will want to have the same program when he migrates from computer to computer.

      I know when I migrated from SuSe to FreeBSD, some of my stuff didn't work right so I had to waste time changing it so that it did work right. However now that I have everything working correctly under FreeBSD there is almost no way in hell I will go back to any of the Linux distros (unless there was an EXTREME incentive to go back, which i doubt will ever happen).

      If someone can come up with a reason why these ports are a waste of time i would really like to know. Until then I will lump them with the other stuff in my 'good things' catagory of software ideas. Also, if someone can come up with a VALID reason why Linux is a better operating system for me to be using, I would really like to know it as well.

  2. FreeBSD programs w/in reach of Linux users? by garcia · · Score: 2

    I thought that most programs (that are of any use) would compile over on FreeBSD would also compile on Linux and vise versa. Doesn't FreeBSD have the ability to run Linux programs w/the same sort of thing?

    What programs would I seriously want to run that are of FreeBSD fame only? None that I know of.

    What do I know though?

    1. Re:FreeBSD programs w/in reach of Linux users? by kilgore_47 · · Score: 2

      Maybe you don't know about them because you aren't a bsd user.
      I'm not a bsd user myself, and I'm curious to see what thas to offer (when I get home from work ;-)

      --
      ___
      The way to see by faith is to shut the eye of reason. --Ben Franklin
    2. Re:FreeBSD programs w/in reach of Linux users? by weav · · Score: 1

      Seems to me the important thing about the "Ports" system is that it automatically fetches the system and all its dependencies and compiles them in one go.

      THe most annoying thing about dealing with RPMs is that I don't find out until "rpm -i" time that it needs 6 other RPMs.

      Thanks to the Port porters...

    3. Re:FreeBSD programs w/in reach of Linux users? by garcia · · Score: 2

      ahhh, even when I ran RH I rarely used RPM unless I was just so lazy I didn't feel like compiling (usually for large libraries, etc)

      I just don't see the point to this. 20mb seems like a lot of space to waste to run applications that should be ported to both OSs anyway.

    4. Re:FreeBSD programs w/in reach of Linux users? by The_Rift · · Score: 1, Informative

      It's the system of installing the software not the software itself.
      Installing a program using the ports tree is as simple as:
      #cd /usr/ports/foo/bar
      #make install clean

      The source is downloaded from one of a list of servers and so are any dependancies. Everything gets compiled and installed and the source code and whatnot is cleaned up afterwards.
      It's one of the biggest reasons I love FreeBSD so much.

    5. Re:FreeBSD programs w/in reach of Linux users? by xonker · · Score: 1

      The cool thing may not be the software available through ports, but the way that software is distributed for BSD. Their ports system seems to be a pretty neat way of distributing software. I'm mostly a Linux user, but also have several BSD boxen at home. They both have their advantages. It's nice (from my point of view) to see any cross-pollination between the two groups.

      It's all Free UNIX, it's all good. At least that's how I look at it.

    6. Re:FreeBSD programs w/in reach of Linux users? by Maditude · · Score: 1
      What programs would I seriously want to run that are of FreeBSD fame only? None that I know of.
      Good point, but I think the point of this exercise was that FreeBSD ports are a handy utility for installing software packages from source, handling all sorts of crazy dependencies for you automagically. The only things I'm not crazy about are: the port-maintainers sometimes pick some pretty weird locations to store things, and: things can get pretty confusing when you upgrade.
    7. Re:FreeBSD programs w/in reach of Linux users? by ichimunki · · Score: 2

      How is the ports system an improvement over Debian's apt-get system?

      --
      I do not have a signature
    8. Re:FreeBSD programs w/in reach of Linux users? by garcia · · Score: 2

      I have Debian.

      apt-get update
      apt-get upgrade

      no wasted time compiling, knows the dependencies I need, and it does everything for me.

      that's just my opinion though.

    9. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      It isn't associated with the FSF.

    10. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      the software you get is the same. the difference with *bsd ports is in the way the software source/binaries are retrieved, built and installed. among other things it means not manually hunting for a suitable mirrors for the software, and then its dependencies. in my limited experience it works really well.

    11. Re:FreeBSD programs w/in reach of Linux users? by Z4rd0Z · · Score: 1

      What do I know though?

      Not very much, about this subject. The ports collection is not software for FreeBSD only. It's a packaging system that takes care of dependencies, in some ways similar to Debian's dpkg.

      --
      You had me at "dicks fuck assholes".
    12. Re:FreeBSD programs w/in reach of Linux users? by Arker · · Score: 2

      How is the ports system an improvement over Debian's apt-get system?

      Last I checked, apt-get was great for binary installs, but not so well suited to local compilation. Ports is the equivelant for people that prefer their binaries locally compiled and optimised for their system.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    13. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      and that would be good because ???

    14. Re:FreeBSD programs w/in reach of Linux users? by zulux · · Score: 2

      The ports collection would come in usefull if apt-get or rpm somehow didn't work properly for you. The ports system seems very robust on my FreeBSD box - it takes a long time to compile some of the larger programs, but after coming back after a long cofee break, I've never encountered a problem. It would be a great backup to have around just in case.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    15. Re:FreeBSD programs w/in reach of Linux users? by FreeUser · · Score: 5, Insightful

      How is the ports system an improvement over Debian's apt-get system?

      First, I am a real fan of Debian, apt-get, and am running debian both at work and at home. .deb's and apt-get are IMHO as good as it gets when distributing, managing, and upgrading binary packages.

      What the FreeBSD ports system does which is so cool is get rid of the idea of distributing binaries at all. Instead, you go into the subdirectory corresponding to the program you want and type "make install." Based on the skeleton files present the program source(s) and any patches are downloaded, applied, the program is then compiled against whatever libraries you have on your system (no more "this binary requires glibc version Y but you only have X"), and installs the compiled binary. Furthermore, doing so is as easy as installing a .deb or .rpm, meaning relatively inexperienced users can do this. Dependencies are simpler (you only need what is required to compile the program, and such dependencies are also automatically downloaded and compiled at the same time. You do not need particular software versions based on what the binary was compiled against.)

      Basically, it combines "apt-get source --compile; dpkg -i [new-packages].deb" into "make install," and simplifies the package management/dependency management.

      BSD ports is IMHO the only software management system that in some ways exceeds even debian's approach, but keep in mind there are conceptual differences to the approach (all things source vs. precompiled binaries), so it isn't entirely an apples to apples comparison.

      --
      The Future of Human Evolution: Autonomy
    16. Re:FreeBSD programs w/in reach of Linux users? by mvc · · Score: 1

      I'm a Debian user too, and I dearly love apt-get, but I must say, I've often wished for something like FreeBSD's ports system for the times when I need to compile something myself. I know about--and use--apt-get source, but it's not aware of dependencies (FreeBSD ports is, as I recall), it's harder to do customized configurations (thought I suspect this is a result of my own stupidity), and it won't install packages into your home directory.

      --

      --Moss

      This is a .sig.
      Now there are two of them.
      There are two _____.
    17. Re:FreeBSD programs w/in reach of Linux users? by iso · · Score: 2

      I've recently started using OpenBSD and I had heard how ports and packages were functionally equivalent to Debian's apt-get (with which I am most familiar). I was very disappointed to find out that while packages and ports are nice, they're nowhere near as nice as apt-get.

      First of all with ports, you have to compile everything yourself, which can take a lot of time on slower machines (like my home router/firewall). In the end it just creates an OpenBSD package anyway.

      So I tried packages. They're pre-compiled, like debs, but the pkg_add software is terrible! In order to update a package you have to first remove the package then add it again! And if the package has dependancies you have to remove all the dependancies and re-install them all again! Plus you can't just do a "pkg_add foo," you have to do a "pkg_add ftp://ftp.openbsd.org{blabalbla}/foo-3.17-2.pkg," which means you not only have to know where to get the file, you also have to know the version number and all other information in the filename in advance! Add to this the fact that there's no real comparable substitue to "apt-get update;apt-get upgrade," and it's quite obvious that OpenBSD's packaging system is woefully inadequate.

      I'm not sure if FreeBSD's paackaging system is better, but I was shocked to see just how bad OpenBSD's packaging was. It's too bad, because apart from the packaging management, I love OpenBSD. Perhaps I'll start working "apt-get-izing" OpenBSD. Has anybody else started such a project? It seems badly needed.

      - j

    18. Re:FreeBSD programs w/in reach of Linux users? by The_Rift · · Score: 0

      Correct me if I'm wrong but doesn't apt-get use binaries? The ports tree also make provisions for upgrading and various options can bet set by editing the make file.
      I haven't used apt-get, but I've heard it comapared to the ports tree regualarly.

    19. Re:FreeBSD programs w/in reach of Linux users? by The_Rift · · Score: 0

      Binaries are bigger, and some licences don't allow for binary distribution.

    20. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      The FSF stands for enslavement, quite contrary to its name. Freedom isn't created through restrictive licensing.

      Closed source licensing, against which the FSF rails, is very restrictive because the user doesn't get the right to use the licensed software as he sees fit. GPL licensing restricts the user from developing so licensed software as he sees fit.

      It's just restrictive at another level than fully closed licenses. But make no mistake, it too is fully closed too.

    21. Re:FreeBSD programs w/in reach of Linux users? by psavo · · Score: 1

      > I have Debian.

      >apt-get update
      >apt-get upgrade

      >no wasted time compiling, knows the dependencies I need, and it does everything for me.



      So do I. The ONLY thing I think apt-get misses is capability to selectively recompile programs for YOUR architecture.
      Debian (I think) is still compiled for 386. Now if you have Athlon 20THz, you miss all the MMX, MMX+, SSE, SSE2, 3DNow!, and all ather nice things.
      Probably your only thing that's compiled for your precious proc. is your kernel. How about glibc, XFree86 and all the other fon things?
      Now THAT'd give you some more edge...

      --
      fucktard is a tenderhearted description
    22. Re:FreeBSD programs w/in reach of Linux users? by Glytch · · Score: 2

      Sounds like an ideal system to add to Slackware.

    23. Re:FreeBSD programs w/in reach of Linux users? by lemox · · Score: 3, Informative

      While it doesn't do dependancies like ports, the following will do what you want:

      # apt-get install pentium-builder
      # less /usr/share/doc/pentium-builder/README.Debian

      apt-get source whatever -b

      pentium-builder is pretty handy IMHO.

      --

      "We obviously need a new moderation category: (-1, Woo-fucking-hoo)" --Mr. AC

    24. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      Baah like a sheep, k.

    25. Re:FreeBSD programs w/in reach of Linux users? by ethereal · · Score: 2, Interesting

      So, I'm curious - what happens when you upgrade one of your big system libraries this way? Does the ports system automatically recompile any affected apps, or re-fetch them, or what? Not that I'm saying Debian necessarily handles this any better (I wouldn't know). Heck, at least with a packaging system, you know what the dependencies are for various apps. If everything's built from source, do you even know which apps were built against which library versions?

      --

      Your right to not believe: Americans United for Separation of Church and

    26. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      You need quite a computing power and good network connections to use the ports systems on a desktop ona daily basis. I've used all three BSD-s and they completely suck dick compared to Debian as far as package management is concerned. Now if only Debian had binary deltas instead of downloading whole packages...mmmmm

      For all practical purposes BSD is dead.

    27. Re:FreeBSD programs w/in reach of Linux users? by quartz · · Score: 1

      If you go here and search for any particular RPM, you can see what it needs before downloading it.

    28. Re:FreeBSD programs w/in reach of Linux users? by sbeitzel · · Score: 3, Insightful

      Well, actually, this won't provide you with any new programs. What this is really about is giving everybody FreeBSD's version of apt-get-source (from what I understand of Debian).

      My guess is that this tarball differs from the ports tree that's available via cvsup (cvsupXX.freebsd.org, where XX is some number on the interval [1,10]) in that the cvsupped ports contain patches that are FreeBSD specific, while this tarball will have settings more appropriate for Linux, such as /tmp rather than /var/tmp, /usr/bin instead of /usr/local/bin, /etc/rc.d instead of /usr/local/etc/rc.d, et cetera.

      --
      Oh, go on, check out my job.
    29. Re:FreeBSD programs w/in reach of Linux users? by then,+it+was+nigh · · Score: 1

      I know about--and use--apt-get source, but it's not aware of dependencies [...]

      Actually, I think apt-get -b source will follow build dependencies (the Build-Depends: line in debian/control), which IINM is essentially the same thing that the ports are doing. Of course, it will also try to compile the package immediately after downloading it, which is counterproductive if you wanted to modify the package before building it; it would, I agree be useful to have a more fine-grained option there.

      --
      sed 's/In Soviet Russia/In NSA America/g' < yakov-smirnoff-jokes.txt
    30. Re:FreeBSD programs w/in reach of Linux users? by high · · Score: 2, Interesting

      Im using APT 0.5.3 and I can do:

      apt-get build-dep

      From the help of apt-get:
      build-dep - Configure build-dependencies for source packages

      This should do pretty mush what ports do!

    31. Re:FreeBSD programs w/in reach of Linux users? by Brian+Feldman · · Score: 2, Insightful

      Upgrade a system library in what way? If a library is upgraded to a newly-incompatible API/ABI, the version number will be bumped so everything which used to use it will remain doing so until it is recompiled (and possibly adapted if it used an API in a deprecated way). APIs don't usually get deprecated, but ABIs changing isn't unheard of.

      --
      Brian Fundakowski Feldman
    32. Re:FreeBSD programs w/in reach of Linux users? by ethereal · · Score: 1

      OK, that makes sense. For some reason I was thinking that older library versions would be replaced. Thanks for setting me straight.

      --

      Your right to not believe: Americans United for Separation of Church and

    33. Re:FreeBSD programs w/in reach of Linux users? by sammy+baby · · Score: 2

      ...and then, you can follow each link to find out what new dependencies you'll have to satisfy. And so on, ad nauseaum.

      On the Debian system I put together last week (a near-minimal install), I typed "apt-get install mailman" this morning. A second later, it responded by saying would also need to fetch apache, apache-base, and python-base, and did I still want to continue?

      Speaking as a former RedHat user (and a guy who has logged many hours poring over rpmfind.net), I have to say that apt-get is really easy to get used to.

    34. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      apt uses either binaries or source; normal usage is binaries.

    35. Re:FreeBSD programs w/in reach of Linux users? by quartz · · Score: 1

      Look, I wasn't trying to diss Debian. I run it myself on my laptop, and I quite enjoy the simplicity of apt. On the other hand, I thoroughly enjoy tinkering with the innards of my system and occasionally breaking stuff (that's how I learn best), and for that purpose rpm seems to me more powerful and versatile, but hey - to each his own.

    36. Re:FreeBSD programs w/in reach of Linux users? by Arandir · · Score: 2

      You need quite a computing power and good network connections to use the ports systems on a desktop on a daily basis.

      How many packages do you install on a daily basis? I upgrade a port/package about once every two weeks. The first time you install it takes a while, but after that you don't have to worry about it anymore. Or you can initially install only the prebuilt packages, and only use ports for upgrading.

      FreeBSD is free, as in speech, beer, and not telling you how to maintain your system.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    37. Re:FreeBSD programs w/in reach of Linux users? by znu · · Score: 2

      The Ports system is great on non-x86 hardware. I run NetBSD on an old Power Mac. It used to run Linux (various distros). I frequently cound't find pre-compiled stuff, and compiling myself often failed. I've yet to have any installation via the Ports system fail on me.

      --
      This space unintentionally left unblank.
    38. Re:FreeBSD programs w/in reach of Linux users? by sir_nas · · Score: 2, Informative

      yes, but also dont forget that bsd also has a pkg_add command. when used with the -r switch, ir downloads binaries of whatever you are trying to install, ie: pkg_add -r kde or whatever, and will also fetch dependicies. so you sort of get the best of both worlds, you can either use ports to compile from source, or you can be lazy and use pkg_add to grab the binaries w/deps.

    39. Re:FreeBSD programs w/in reach of Linux users? by psavo · · Score: 1

      >While it doesn't do dependancies like ports, the following will do what you want:
      ># apt-get install pentium-builder
      ># less /usr/share/doc/pentium-builder/README.Debian
      ># apt-get source whatever -b

      >pentium-builder is pretty handy IMHO.

      Thanks!
      That was a real nice one. I shall try to recompile at least perl (you know how much perl code there is..), bash should be nex.. uh boy..

      Thanks again!

      --
      fucktard is a tenderhearted description
    40. Re:FreeBSD programs w/in reach of Linux users? by rainer_d · · Score: 1

      Yes, it's great.

      I use FreeBSD almost exclusively, but I must say, it has its limits:

      Just consider something like KDE2 - I can't imagine compiling this beast on my home system
      (Dual P2-450/512 10K RPM Barracuda) without letting the computer run for at least the whole weekend - if that is enough.

      We can't have Joe Newuser let his computer run for a week or two during initial install.

      Also, the ports-system seems to break the packages in that upon installing a release from CD you realize that the pkg-plist was incorrect or some script is not run correctly.

      --
      Windows 2000 - from the guys who brought us edlin
    41. Re:FreeBSD programs w/in reach of Linux users? by LoneRanger · · Score: 1

      Depends on what you mean, I'll assume you mean that the major version number went up. In that case you use a really cool piece o' software called portupgrade...You run portupgrade with the package who's major number changed and it finds all packages that require it and recompiles them. It takes a while, but it's worth it.

      I just did a portupgrade and png-1.2.0 the other day and it took all day to do it (Dual P3 600s), but it was worth it. I got all my fun little compiler flags in and everything fits my system like a glove.

    42. Re:FreeBSD programs w/in reach of Linux users? by blafasel · · Score: 1

      also, did you ever try to run apt-get as a mere mortal luser? it's truly peachy. debian is cool, but it has it's limits. distribution of software in source form is, IMHO, the way to go; with binary distributions as an option, not the other way round.

      --

      check your speling
    43. Re:FreeBSD programs w/in reach of Linux users? by MikeMc · · Score: 1

      The OpenBSD ports system is closely tied to OpenBSD OS releases. When you upgrade to a new OS release, usually an updated tarball of the ports tree is released as well. The ports system is not really intended to be "tracked" with the latest and greatest version of the ported program out in the wild.

      --
      Marco...that was Portugese.
    44. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      Don't you mean crapt-get.. or fuck-up-your-system-beyond-repair-get ???

      - Linux Lover.

    45. Re:FreeBSD programs w/in reach of Linux users? by skbenolkin · · Score: 2, Informative

      Point taken, to some extent, but for FreeBSD, there's pkg_update .

      --
      "Frederick, is God dead?" --Sojourner Truth
    46. Re:FreeBSD programs w/in reach of Linux users? by chill · · Score: 1

      I've got a very similar setup: Dual P3-450, 512 Mb and some 10K UltraSCSI drives.

      For the record, KDE 2.2.1 and related packages took 8 hours to compile and install.

      That doesn't include downloading...oops, need that package too...download...repeat for 2 hours.

      --
      Learning HOW to think is more important than learning WHAT to think.
    47. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      What do you know? Not much, apparently. The ports tree is a simple, easy, and massively flexible system that allows you to download, configure, compile, install, and remove software, all in about 3 commands. It also provides and uses patches for people that suck and write code that does not easily compile on a system as widely standardized as BSD UNIX.

      By the way, it kicks the shit out of any linux distro's means for installing 3rd party software.

    48. Re:FreeBSD programs w/in reach of Linux users? by spacehunt · · Score: 1
      While it doesn't do dependancies like ports

      Perhaps you're after apt-get build-dep whatever ?

    49. Re:FreeBSD programs w/in reach of Linux users? by James+Lanfear · · Score: 1

      The real problem with building KDE isn't the time, it's the space. I recently did a fresh FreeBSD install with a 3.5GB /usr, and then built KDE. When it stopped 6 hours later I had 16.4MB left, and I ended up spending the last half-hour hovering over the console waiting for everything to fall apart when I ran out of disk. Now I build and clean the major packages one at a time, because I can't afford to leave half my drive free. At least KDE is stable enough that you can go for months without updating if need be.

    50. Re:FreeBSD programs w/in reach of Linux users? by Anonymous Coward · · Score: 0

      I agree, Slackware is almost FreeBSD like (thier installs are almost identical) so this might be the perfect addition.

  3. What is GNU/Linux? by Anonymous Coward · · Score: 1, Funny

    Is it like Linux?

    1. Re:What is GNU/Linux? by Anonymous Coward · · Score: 0

      Yes, except it's Free, whereas Linux is proprietaty.

    2. Re:What is GNU/Linux? by Anonymous Coward · · Score: 0

      Where can I get GNU/Linux? Redhat only sells Linux.

    3. Re:What is GNU/Linux? by Anonymous Coward · · Score: 0

      What does GNU stand for? I have heard that it is some kind of gay slang. Is that true?

    4. Re:What is GNU/Linux? by sup4hleet · · Score: 1

      Nah GNU/Linux is more like Unix(tm)
      :)

    5. Re:What is GNU/Linux? by garcia · · Score: 2

      I am sick and tired of the GNU/Linux / Linux arguement.

      Call it whatever you want, just don't call it Microsoft/Linux. ;-)

    6. Re:What is GNU/Linux? by Anonymous Coward · · Score: 0

      GNU = the Gay Narcissists Union

    7. Re:What is GNU/Linux? by glan · · Score: 1

      Richard Stallman pointed ou that since Linus Torvalds used some GNU programs in developing his OS this could be acknowledged by calling the new OS GNU/Linux. Nothing wrong with that!

    8. Re:What is GNU/Linux? by grepnyc · · Score: 1

      >>Richard Stallman pointed ou that since Linus Torvalds used some GNU programs in developing his OS this could be acknowledged by calling the new OS GNU/Linux. Nothing wrong with that!

      Doesn't roll off the tounge too easily.

      Kind of like GNU/Perl
      GNU/Python
      GNU/Doom Port
      GNU/MySQL

      pressure/grep

      --


      Microsoft Fucking Sucks!! Up The Penguins!!
    9. Re:What is GNU/Linux? by jerdenn · · Score: 2

      Richard Stallman pointed ou that since Linus Torvalds used some GNU programs in developing his OS this could be acknowledged by calling the new OS GNU/Linux. Nothing wrong with that!

      Yup, and Symantec writes a lot of their software in Microsoft Visual C++, but we don't call it Microsoft / Norton AntiVirus, do we?

      -jerdenn

  4. GNU/Linux by DrXym · · Score: 5, Funny

    Note to BSD folks: It's Linux, not GNU/Linux.

    1. Re:GNU/Linux by Anonymous Coward · · Score: 0

      Now it's BSD/Linux!

    2. Re:GNU/Linux by mr_don't · · Score: 1

      Actually,

      "Linux" is the name of a kernel, the core and basic input/output mechanism of an operating system, while the term "GNU" refers to the entire operating system as a whole. GNU attempts to be available for other kernels, such as the HURD, and some GNU programs can be used on top of, for example, Windows or other sorta-posix compliant systems such as BeOS. Most people who use the Linux kernel are running a huge suite of programs provided by the developers working both alone and in conjunction with the Free Software Foundation.

      I wonder what the goal is of dening the Free Software Foundation credit for things such as the GPL and kicking off gcc, etc.?

    3. Re:GNU/Linux by Anonymous Coward · · Score: 0

      You're right. I'll now commence calling my systems SAP/AS400 from now on.

    4. Re:GNU/Linux by Anonymous Coward · · Score: 0

      Where did you get your info? Linux is just one small little file... then everything around (just about) is from GNU... that is your redhat, debian, etc. all use the same crap around the linux kernal.

      (note the use of crap is not saying anything about gnu nor linux in general... its just saying the stuff around it)

    5. Re:GNU/Linux by Anonymous Coward · · Score: 0

      Thanks, DrXym. Or is that Asshole/DrXym?

    6. Re:GNU/Linux by Reality+Master+101 · · Score: 3, Insightful

      I will never, ever call Linux by that name. If I ever meet RMS, I won't use the term, either. He can correct me over and over (as he is notorious for doing), and I will never, ever EVER EVER use that idiotic term.

      My goal is to not cave in to the "language police". The GNU component is only one component of a Linux distribution. The Kernel is called Linux. A distribution is typically called Linux. I am not confused by this. Most people are not confused by this.

      I wonder what the goal is of dening the Free Software Foundation credit for things such as the GPL and kicking off gcc, etc.?

      I wonder what RMS's goal is for denying other parties credit for things such as XFree86, Perl, etc. GNU's stuff is only piece. Certainly an important piece, but only one piece.

      --
      Sometimes it's best to just let stupid people be stupid.
    7. Re:GNU/Linux by Bob+The+Cowboy · · Score: 1

      Why?

      So if I only install BSD utils/libs am I then running BSD/Linux?

      What if I pick and choose... or install both? Am I then running GNU/BSD/Linux? At what point does this retardation end?

      Bill

    8. Re:GNU/Linux by poot_rootbeer · · Score: 1


      Interesting statement, Dr. Xym. "It's not GNU/Linux", indeed.

      Oh I get it! "XYM" is just "RMS" ROT13'd. What a clever jape!

    9. Re:GNU/Linux by JohnG · · Score: 2

      Don't FreeBSD and MacOS X also use gcc and other GNU software? Why aren't we forced to call them GNU/FreeBSD and GNU/MacOS X?

    10. Re:GNU/Linux by DrXym · · Score: 2
      GNU refers to the OS as a whole????


      I hate to state the bleeding obvious but major and significant parts of a typical Linux distribution are not GNU. Try to guess which bits. I consider it an insult that the term is blanketed over code (including some of my own) which is neither owned by the FSF nor even GPL in many cases. Certainly the FSF provides some of the bedrock tools for a Linux distro - and we salute them for it - but to name the whole distro in their honour is just silly.


      Linux is a perfectly acceptable term to refer to the whole OS in generic terms or to the kernel. If specific context is needed, prepend Mandrake, Redhat, SuSE etc. as appropriate.

    11. Re:GNU/Linux by rgmoore · · Score: 1
      I wonder what RMS's goal is for denying other parties credit for things such as XFree86, Perl, etc. GNU's stuff is only piece. Certainly an important piece, but only one piece.

      It's particularly ironic that RMS makes such a vigorous complaint about this given that he vigorously (and correctly, IMO) complained about the "practical problems" with the "obnoxious advertizing clause" in the original BSD license. It seems to me that the whole "GNU/Linux" situation represents essentially the same problem. There's no logical reason to include GNU but exclude the other components when naming it, and demanding that GNU be included in the name is exactly the same thing that made the advertizing clause so annoying.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    12. Re:GNU/Linux by Florian · · Score: 1
      You wrote:
      Don't FreeBSD and MacOS X also use gcc and other GNU software? Why aren't we forced to call them GNU/FreeBSD and GNU/MacOS X?
      But unlike in mainstream "Linux Distributions", gcc is the only major GNU component. The libc and toolsets (cat, tar etc.) of the BSDs are non-GNU, same goes for the standard shells. Linux, the kernel, does not amount to a functional operating system on its own. To have a minimal running system, you need a libc, an ld linker, the basic cp/cat/mv... tools and a shell. All major "Linux distributions" - as well as the Linux Standard Base specification - use the Linux+GNU setup for the core OS. (While XFree86, Apache, KDE, Gnome, Samba, etc. are optional components.) So its fair, IMHO, to speak of "GNU/Linux" when we refer to the working operating system (or, if you prefer, the lowest common denominator of the operating system).
      --
      gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
    13. Re:GNU/Linux by Reality+Master+101 · · Score: 2

      In fact, I think I'm going to start calling it KDE/Linux. I would imagine that would REALLY irritate him.

      --
      Sometimes it's best to just let stupid people be stupid.
    14. Re:GNU/Linux by Anonymous Coward · · Score: 0
      If I ever meet RMS,


      What, are you looking for a job carrying jockstraps?

      You are not up to the job.

      Hell, you don't even have the balls to use your real name online. Or were you named RM when you were whelped?

      my sympathies.

    15. Re:GNU/Linux by Anonymous Coward · · Score: 0

      Personally I thank god that linux distributions use the GNU components. BSDs toolsets are annoying... Just one more nail in the coffin.

    16. Re:GNU/Linux by Reality+Master+101 · · Score: 1

      What, are you looking for a job carrying jockstraps?

      I don't think RMS wears any sort of underwear.

      Hell, you don't even have the balls to use your real name online.

      I hope you see how amusing that is.

      Actually, I used to use my real name and e-mail on Slashdot, but I got tired of the l33t Script Kiddies attacking my box because they disagreed with my post. Who needs the hassle.

      --
      Sometimes it's best to just let stupid people be stupid.
    17. Re:GNU/Linux by cobar · · Score: 2

      FreeBSD also includes a few other gnu tools. grep, tar, binutils and awk are all FSF versions. While they'd like to have BSD licensed versions, they either were removed from the 4.4-lite sources or the gnu versions were much better than the alternatives at the time.

      There are quite a few others like cvs, groff, etc. that aren't really essential but are part of the system too.

      One interesting thing I just noticed is that the version of IPFilter that's in the tree has a new license that does allow redistribution:

      Redistribution and use, with or without modification, in source and binary
      forms, are permitted provided that this notice is preserved in its entirety
      and due credit is given to the original author and the contributors.

    18. Re:GNU/Linux by Enahs · · Score: 2
      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.

      --
      Stating on Slashdot that I like cheese since 1997.
  5. RPM for the people? by richie2000 · · Score: 1
    (make install of the whole thing)
    That would typically take at least a week and over 20gig total, but it is worthwhile to do.

    A week? Well, maybe it's time for that vacation...

    --
    Money for nothing, pix for free
    1. Re:RPM for the people? by steveo777 · · Score: 1
      Or 200+ years on a 56K modem. Ugh... living in the sticks (or somewhere past them) realy does suck for geeks.

      --
      This sig isn't original enough, it's time to come up with something witty...
    2. Re:RPM for the people? by steveo777 · · Score: 1

      Okay, before I get flamed for such a wierd number, I didn't even think about doing the math for this. Let's see then. 20*1024*1024/60/60/24/3 =~ 81 days. Close enough...

      --
      This sig isn't original enough, it's time to come up with something witty...
    3. Re:RPM for the people? by richie2000 · · Score: 1
      I once gave a lecture on modem standards, bandwidth and transmission speeds. I used a leeched copy of MS Office 97 as my yardstick - on a 14.4 modem it would take x days to download while with a 56K you'd be up and violating the EULA within hours. :-)

      BTW, I assumed the author meant it would take a week to compile (he probably didn't do the math either - it's scary if he did) and use up 20 gigs of diskspace, but I'm not sure.

      --
      Money for nothing, pix for free
    4. Re:RPM for the people? by Anonymous Coward · · Score: 0

      Hey, at least you've never installed Microsoft Office 2000 and Microsoft Visual Studio Enterprise Edition over a serial connection (ye old "Direct Connect"). Which comes to to something like 115kbit, or 14000 bytes per second. Now that is pain.

  6. Oh well by absurd_spork · · Score: 1
    I already hear them screaming, "That's like stealing precious BSD software for Linux!"


    But then, the FreeBSD port/package system is still the best one I've ever had the pleasure to work with, especially because of its good source/binary interoperability.

    1. Re:Oh well by Anonymous Coward · · Score: 0

      Don't you get it? BSD people *want* people to do this kind of stuff. BSD folks want people to be able to use their work on other platforms.

      BSD is FREEDOM. It's the GPL folks who are crying that everyone's trying to usurp their freedoms at every turn. Meanwhile, the BSD people are happily donating code all over the place.

      You would think being (FSF) Free would make you happy. It seems it just makes you grouchy.

    2. Re:Oh well by Kwikymart · · Score: 1

      I already hear them screaming, "That's like stealing precious BSD software for Linux!"

      The only main problem with that statement of yours is that you are stupid. The only way you can "steal" BSDL code is to remove the copyright notice from either the source or not include it in the binary distribution. Even then it is not considered "stealing". Just look up the definition of "steal" in the dictionary before you post stuff like this. Its more commonly Linux people talking about "Microsoft stealing FreeBSD code". So please, until you know what you are talking about do not spread this kind of FUD around.

      --

      Buying a Dell computer is equivalent to dropping the soap in a prison shower.
  7. Open Packages by Z4rd0Z · · Score: 2, Informative

    I don't know how many times I wanted to do this, but always got bogged down in the details. The OpenPackages project has had their system working on Linux for a while now. However, OpenPackages departs from the FreeBSD ports collection and takes a lot from OpenBSD and NetBSD as well. And it's not finished yet. Work seems to have slowed down on it too, unfortunately.

    --
    You had me at "dicks fuck assholes".
    1. Re:Open Packages by kilgore_47 · · Score: 1

      In the beginner's mind there are many possibilities. In the expert's mind there are few. --Suzuki-roshi

      So being certain and closed mined makes one an expert? I don't like that quote at all!
      Maybe it should read In the young mind there are many possibilities. In the elderly mind there are few.

      (yes I know replying to sigs is passe and even modbait, but I just couldn't resist. At least I'm not using my +1 bonus!)

      --
      ___
      The way to see by faith is to shut the eye of reason. --Ben Franklin
    2. Re:Open Packages by Anonymous Coward · · Score: 0

      The quote never says to be closed minded is to be an expert. It says to be an expert is to have fewer possibilities in one's mind. That isn't the same thing. Also, don't take it too literally.

    3. Re:Open Packages by Anonymous Coward · · Score: 0

      thanks for the clarification, Suzuki-roshi.

    4. Re:Open Packages by Anonymous Coward · · Score: 0

      You are welcome, my son.

  8. Linux Portage by Anonymous Coward · · Score: 0

    If you want a better designed port system for linux try Http://www.gentoo.org. Gentoo Linux rocks!!

  9. Oh no ! by Anonymous Coward · · Score: 0, Offtopic

    BSD is undead !
    Get off Linux you ugly zombies !

  10. hunh? by Guns+n'+Roses+Troll · · Score: 0, Offtopic

    testing, ignore this shit

    Slashdot requires you to wait 20 seconds between hitting 'reply' and submitting a comment.

    It's been 10 seconds since you hit 'reply'!

    If you this error seems to be incorrect, please provide the following in your report to Source Forge:

    Browser type
    User ID/Nickname or AC
    What steps caused this error
    Whether or not you know your ISP to be using a proxy or some sort of service that gives you an IP that others are using simultaneously.
    How many posts to this form you successfully submitted during the day* Please choose 'formkeys' for the category!
    Thank you.

  11. Sounds nice to me by famazza · · Score: 1

    To tell the truth I've never used *BSD ports. I hear a lot that they are wonderful. I don't know how it works, but I'm sure that I'll try it.

    The only thing I hope is that they let every choices to me. I use slackware and tarballs for one reason: the word automatic have been sounding weird for me.

    Since I got tired of Mandrake and rpm automatic for me means this:

    • In a way somebody though it was better, not necessarily the way I need or want.

    Hope not to find this kind of automation with ports.

    --

    -=-=-=-=
    I know life isn't fair, but why can't it ever be un-fair in MY favor!?
    1. Re:Sounds nice to me by Arandir · · Score: 2

      The only thing I hope is that they let every choices to me. I use slackware and tarballs for one reason: the word automatic have been sounding weird for me.

      You can do the same under FreeBSD as well. There are prebuilt binary "packages" that are essentially identical to Slackware tarballs.

      What is great about ports is that you get all of the benefits of building from scratch, with the convenience of automatic builds, dependency checking, etc.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Sounds nice to me by Steeltoe · · Score: 1

      Not that I know Slackware, or have ever tried it. But I thought the whole point of Slackware was to build from source yourself. So what are these "prebuilt binary packages"?

      - Steeltoe

    3. Re:Sounds nice to me by Arandir · · Score: 2

      I think Gentoo and LFS Linux are the only distros where you have to build everything from scratch. Everybody else has prebuilt packages. Even Slackware. I mean, nobody wants to go out and spend their entire three day holiday weekend *installing* the system! So you use packages instead.

      I've built FreeBSD up from scratch from the base OS to XFree86 to KDE and all of their dependencies. Even on mostly autopilot, it took a three day weekend. Now I take a different tack. I install everything I want from a package, then recompile them in the background later, so at least I have a system I can *use* in the meantime.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    4. Re:Sounds nice to me by Enahs · · Score: 2
      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.)

      --
      Stating on Slashdot that I like cheese since 1997.
  12. Why not use the real thing? by Anonymous Coward · · Score: 0

    If you want FreeBSD ports, user FreeBSD. DUH :)

    1. Re:Why not use the real thing? by Anonymous Coward · · Score: 0

      Exactly.

      P.S
      Slashdot requires you to wait 20 seconds between hitting 'reply' and submitting a comment.

      It's been 18 seconds since you hit 'reply'!

      If you this error seems to be incorrect, please provide the following in your report to Source Forge:

      * Browser type
      * User ID/Nickname or AC
      * What steps caused this error
      * Whether or not you know your ISP to be using a proxy or some sort of service that gives you an IP that others are using simultaneously.
      * How many posts to this form you successfully submitted during the day

      * Please choose 'formkeys' for the category!
      Thank you.

    2. Re:Why not use the real thing? by Anonymous Coward · · Score: 0

      what if I want ports so I can effortlessly compile apache while at the same time I'm playing Quake3, accelerated, on my Nvidia card?

    3. Re:Why not use the real thing? by Anonymous Coward · · Score: 0

      Install Windows. Simple as that.

  13. Ports++ = Gentoo by polarbear · · Score: 1

    Anyone remotely interested in this should be checking out a fairly new distribution called Gentoo which is working towards their 1.0 release. You can build your entire system just by booting from a cd image, formatting, untaring a small build image, setting up network, and installing everything from their advanced ports like system called "portage". Its basically ports++ that forms the core of the distro (aka its not just for "third party packages").

    It supports stuff like profiles, etc so by editing a few text files you can define your which specific packages and versions should be installed, etc (basically define your own distro ;) Plus Gentoo is currently in the progress of testing its new dependency based init script system (no sysvinit or bsd init scripts here) and working on some other cool ideas.

    Definatly check them out, there is no other distribution or OS quite like it! :)

    BTW, the url is http://www.gentoo.org

    --
    --- polarbear
    1. Re:Ports++ = Gentoo by Z4rd0Z · · Score: 1

      Yeah, I've tried it and it definitely has potential. Once they're a little more mature, I'll probably trade Debian for it.

      --
      You had me at "dicks fuck assholes".
    2. Re:Ports++ = Gentoo by flynn_nrg · · Score: 2

      "Its basically ports++ that forms the core of the distro (aka its not just for "third party packages")."

      Please, read the FreeBSD handbook :)

      cd /usr/src && make -j8 buildworld

      I installed FreeBSD 4.3 on my box when it was released, I CVSuped the latest source code last week and now my box reads:

      ainhoa# uname -srn

      FreeBSD ainhoa.energyhq.org 4.4-STABLE

      Yep, FreeBSD is cool :)

    3. Re:Ports++ = Gentoo by Anonymous Coward · · Score: 0

      Sounds like OpenBSD's way of doing things - by your description so far.

  14. Can someone explain why I would want this? by mj6798 · · Score: 2

    Both on RedHat and on Debian, installing software either from source or from binary is trivial. And almost all the software I have ever wanted has been packaged for Linux distributions. Why would I want the BSD ports? Is there any software that I don't know about that I am missing?

    1. Re:Can someone explain why I would want this? by Anonymous Coward · · Score: 0

      Ports is source!
      You can also make a package from it, you can also download the same source (compiled from a ports tree) and pkg_add it, fully automated etc.. /usr/ports 0wnz!

      It takes care of all dependencies, etc.. no need to fuss around looking for a library dependcy, etc.. ports does it all for you and automates it. You can sync it via, cvs etc.. etc... and pkg_version -c > file to see what ones need to be updated, blah blah blah... Ports Tree is better than anything I've seen so far. Nothing can be easier, not to mention you still have 100% full source access and compile options, etc.. read the man pages for more details...

      have a good one!

    2. Re:Can someone explain why I would want this? by Anonymous Coward · · Score: 0

      I don't mind at all explaining this to you at all. It isn't missing software that's the issue, it's missing functionality. RedHat might have the ability to "trivially" upgrade binary packages within a major release, but it is virtually imposisble to upgrade the entire system to a new major release without running into major problems. I haven't had a lot of Debian experience, except for being able to point out the the tulip driver for the network install method doesn't properly include tulip drivers (which is why I don't have a lot of experience with Debian :)).

      Try installing a RH 6.2 system, then upgrading to the latest KDE version.

    3. Re:Can someone explain why I would want this? by CentrX · · Score: 1

      Red Hat does not take care of dependencies for you at all, you have to compile it and then it comes up with a compile error because you don't have some header file, but which package contains that? who knows!?

      Debian is much better, but installation from source is not quite as trivial as with BSD ports.

      --

      "The price of freedom is eternal vigilance." - Thomas Jefferson
  15. gentoo linux by snorks · · Score: 1

    gentoo linux has a similar system called portage. You can download a 40M bootstrap iso and build your entire system using portage. This is a wonderful distro.

    1. Re:gentoo linux by stfrn · · Score: 1

      how does one go about downloading gentoo? i'm ibntersted in it, but all i can find on the website are links for the prerelease, and the iso images. no real help for a newbie(who doesn't have a cd-rom).

      --
      "It'll be like stealing candy from a baby... why, that look like a lark!" - Mr. Burns.
    2. Re:gentoo linux by Anonymous Coward · · Score: 0

      As a note, Gentoo specifically mentions the FreeBSD ports collection as the origin of there "portage" system. hence the name "portage".

  16. Veering slightly OT - the goal by Arker · · Score: 1

    I wonder what the goal is of dening the Free Software Foundation credit for things such as the GPL and kicking off gcc, etc.?

    It's usually motivated by personal hatred for RMS it seems. The guy has strong ideals and has refused to compromise them. In a world where corruption and compromise is the norm, this naturally pisses a lot of people off. Even people that rely on software that exists because of his refusal to compromise. Those are the ones that are most virulently opposed to giving him any credit at all, naturally.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:Veering slightly OT - the goal by Anonymous Coward · · Score: 0

      Demanding that GNU be placed in front of Linux is hypocritcial. The GNU demand is advertising for the GPL, for the FSF, for RMS himself and his ideals.

      Yet, you'll recall, the original BSD license contained an advertising clause that made it incompatible with the GPL.

      Why is advertising not allowed for others, but Stallman demands it for himself?

  17. Compile flags by flynn_nrg · · Score: 3, Informative

    I prefer to compile with these options in my /etc/make.conf

    CPUTYPE=i686

    This way you automagically have a cc -O -pipe -march=pentiumpro setup so you don't compile for 10 years old 386 cpus.

    Sure, compiling KDE2 will take some time, but who cares, you can continue working while the package builds, thanks God for dual cpus and SCSI disks :)

    1. Re:Compile flags by The_Rift · · Score: 0

      Thanks for that! Gonna tweak my config now!

    2. Re:Compile flags by Anonymous Coward · · Score: 0

      Just how much faster is X, KDE, glibc, etc when compiled i686 (or 586 or Athlon)? Anyone know of any benchmarks?

  18. It is RMS/Linux by Anonymous Coward · · Score: 0

    You know that deep down, that is what he wants it called.

  19. It's about time.... by zentex · · Score: 1

    hopefully now all them Linux users will see what kinda nifty toys us BSD users have been using since the invention of the toaster...

    ...and then (oops, here comes the conspiracy theory) after said Linux users like the ports system, they will stop using Linux and start using BSD...(yea yea, shuddup, it's humor).

    *yaay*

    --
    Appended to the end of comments you post. 120 chars.
    1. Re:It's about time.... by guacamole · · Score: 1

      Oh please. Ports seem to be so primitive.

      On Debian you just type

      "apt-get install progname"

      and the binary package is downloaded and installed. On RedHat you can just type:

      "up2date -i progrname" and it will be downloaded and installed. Why would I want to both with ports which seem not to work half the time even on *BSD?

    2. Re:It's about time.... by Anonymous Coward · · Score: 0

      rofl, you certainly haven't used it enough to know how much better it is than aptget or whatever fragmented linux distro you use.

      pkg_add package.tgz
      pkg_add ftp://ftp.host.com/pub/dir/path/file.tgz
      etc..
      etc..
      etc..

      pkg_* (more pkg_* commands/features) nothing compares yet.
      cd /usr/ports/dir/port/ ; make && make install.
      Takes care of all dependencies for you, no fuss at all! Just sit back and let it take care of everything for you.

    3. Re:It's about time.... by guacamole · · Score: 1
      rofl, you certainly haven't used it enough to know how much better it is than aptget or whatever fragmented linux distro you use. pkg_add package.tgz pkg_add ftp://ftp.host.com/pub/dir/path/file.tgz etc.. etc.. etc..

      And how is that any better than apt-get or up2date? With apt-get or up2date you never have to specify the URL. just run "apt-get install apache-ssl, sit back and relax

      pkg_* (more pkg_* commands/features) nothing compares yet. Bullshit. cd /usr/ports/dir/port/ ; make && make install. Takes care of all dependencies for you, no fuss at all! Just sit back and let it take care of everything for you.

      Bullshit. apt-get and up2date takes care of dependencies for you too. Moreover, you don't have to wait for the stupid thing to compile. Also, I have seen ports fail many times because they're either broken or because the source tar ball does not exist any more on the ftp server.

    4. Re:It's about time.... by Anonymous Coward · · Score: 0

      The reason it probably didn't exist on an FTP server, is the package was really old. It's probably been updated several times since the release, which you never upgraded. Use a cool program in the ports collection called 'cvsupit'. It gets all of the ports info from CVS (updates makefiles, etc etc.) I have never had the experience that you have, nor have I heard of anyone else (capable and willing to invest a bit of time into research--that is) that you seem to have had. FreeBSD, *BSD are really great operating systems, that give you a complete experience. It's the Macintosh of UNIX systems (a big line anymore, huh?), in that the system is designed to operate as a whole(no need to get 3rd party software to get basic things done).

  20. Porting ports.. by RenQuanta · · Score: 2

    I'm an avid FreeBSD user, so I am really glad to see FBSD technology making its way into the Linux camp. I hope many Linux newbies benefit from this. I believe it or not, I found FBSD easier than Linux when I knew nothing about UNIX. The Ports Tree was a huge part of that.

    But let me see if I've got this right...the FreeBSD ports tree is a port of Linux/nonBSD-UNIX based software (mostly Linux based) to FreeBSD, and now someone has taken it and ported it back to Linux...heh.

    (Okay, okay, I realize it's the actual ports tree system which is being ported, but still... ;)

    1. Re:Porting ports.. by Anonymous Coward · · Score: 0

      You got the last part completely wrong.. more like linux (as is the case here) ports from *BSD and 'borrows' code, etc.. 101% certainly not the other way around...

      Yes, I found FreeBSD much easier to learn and hell, even manage than Linux. I've learned a lot more from FreeBSD and OpenBSD in a month than I have from Linux in a year or so. It's just no fragmented like Linux, and it's *standard* no fuss about what distro to run, what kernel, etc.. or, I dunno this distro, but i know this one...

      My $0.02

  21. Re:Veering slightly OT - the curbside cowboys by richie2000 · · Score: 1
    Or should we rename it RMS/Linux?

    I understand RMS' point here, but a Linux distro is much more than just Linus' kernel and a bunch of GNU stuff on top. It seems unfair to single out GNU/FSF/RMS when KDE, Gnome, XFree, MySQL, sendmail.org/Eric Allman, the ReiserFS, Emacs and LVM people and loads of others are just as well-deserved of a honourable mention. GNU doth not a distro make. If RMS keeps this up, some anal types will start compiling alternates for all the GNU utils... How's that for poetic justice?

    Just give it up - GNU's not Linux.

    --
    Money for nothing, pix for free
  22. Its all about the Debians by On+Lawn · · Score: 3, Interesting


    Well, how is this better than Rock Linux?

    Rock's package management system is source based, and updates, etc...

    And as for elitism, I spoke with the creater on the phone a few years ago when he was starting it, and he's a really jolly bloke.

  23. GNU Darwin != GNU / Linux by spring · · Score: 1

    Am I missing something? GNU / Darwin is the base OS in Apple's MacOS X; it is not linux.

    1. Re:GNU Darwin != GNU / Linux by Anonymous Coward · · Score: 0

      GNU Darwin has nothing to do with Apple. It's just a bunch of gnu clowns trying to reimplement all of OS X's base system with under their bizarro-world gnu license.

      Think of a bunch of GNU nutjobs running off to build a Windows 2000 clone, and calling it GNU/W2K. It's the same idea.

    2. Re:GNU Darwin != GNU / Linux by proclus · · Score: 1

      Isn't this trolling?

      Anyways, if you want to know what GNU-Darwin is trying to do, then just read the mission statement. It's right there on the homepage. Any questions?

      Regards,
      proclus

  24. http://www.gentoo.org by BenLutgens · · Score: 1

    This distro has a ports like system natively. But rather than being based on make which wasn't designed for "package managment" it's a set of scripts and applications designed for the purpose. It allows you to install, uninstall and package pieces of software in a sane manner and handles dependancies and virtual dependancies as well.

    In fact the lates rc has a new dependancy based init as well. And it's always loaded with the latest apps and libraries.

    I was a long time debian weenie untill I found gentoo. Now there's no turning back.

    --
    "If you love someone, set them free. If they come home, set them on fire." - George Carlin
  25. Where? by Penguinoflight · · Score: 1

    I hear portage is great too... where can we get it by it's self? (for those of us who don't want to switch distro's.)

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14
    1. Re:Where? by polarbear · · Score: 1

      I'm afraid it really wouldn't be feasable for you to use it on another distribution. Portage _is_ the distribution. There is no seperation between packages in portage and /usr/src like there is in bsd.

      Everything, including kernel, glibc, etc is part of portage. Portage is a distribution building engine that just happens to have default profiles (aka the profile for 1.0_rc6 basically _defines_ a 1.0_rc6 install) for those people who just want to use a distribution and not an engine ;)

      --
      --- polarbear
  26. Local users vs. Root by david.johns · · Score: 1
    Something that no one seems to have made a big deal out of - ports allows you to run it _as a local user_ and have the programs effectively installed in your home directory.

    <doubletake / >

    That's right, you can have that IRC client of your VERY OWN! I hadn't realized that the ports system did this. On the box that I control, I add new software all the time. (apt-get install this-that-and-the-kitchen-sink)

    As much as apt-get rocks, however, you've pretty much gotta be root, and it likes to install things in system-wide locations. So my friend Eugene who really likes links better than lynx has to come ask me to install it, or compile it from source by hand.

    They have solved the problem of software management on a multi-user system, at least when the source is available. Keep in mind that one of the things that has made NT 4.0 horrible to deal with for a large number of people is this very thing. su is your friend.

    Are you an administrator? Oh, well, you can't install this, because it wants to write a registry key HERE and it's not supposed to want to do that. Reboot, become Admin, install, return to being user - maybe software works, maybe it doesn't. (It's not _that_ bad with linux/deb or rpm.)

    AFAIK (IANA Debian God) there is no way to get apt-get to install things in an automated way in the user's home directory. Sure, you can get the source there.. But the really cool thing would be if, not running as root, you ran apt-get and it installed everything in your home directory except that which was already on the system!

    Ooooo... this is cool. Then, when root tries to install the same thing, maybe it could check the signature of the package the local user has downloaded and install it systemwide if the signature matches the one from the debian repository. <div voice="hick">Hee-HEE! Hawt damn!</div>

    1. Re:Local users vs. Root by |_uke · · Score: 1

      this is not a new concept.

      At my previous company we where using solaris systems... Unfortunatly they where pretty out of date and me, being a web developer... could not do anything about it.

      So what did I do? I installed all my fav gnu tools under my home directory. I had a complete working gnu system under my home directory, seperate from everything else. Although I admit, it was a bit harder than using ports, it was still pretty simple.

      ./configure --prefix=$HOME
      make install

      :)

      --
      Luke
    2. Re:Local users vs. Root by david.johns · · Score: 1
      Oh, yeah. I know what you're talking about. I was just marveling at the fact that ports lets you do something that you have to do by hand if using apt-get.. and apt-get would let you do something even cooler if it had non-root-user uses. ;)

      Actually, one fun thing that I have done before, too - tar gz an install of your favorite gnu/linux, save it somewhere. un-tar-gz it into a subdirectory somewhere, and play with chroot. It's nice. (It works best if you've got root on the box, though.) For a while I was running a hybrid of debian unstable and stable on the same box by having a chroot'd unstable install. ;)

    3. Re:Local users vs. Root by proclus · · Score: 1

      Nice to see that somebody "gets it". Thanks guys.

      In the old days, when we were all users, and the sysadmin was god, I had to learn to install applications in my home tree. Now, I can just untar this thing, and I have semi-automatic access to several thousand free software applications. No more going to the admin to ask(beg) for software installation. You don't need his permission anymore. =}

      Yes, it is possible to do this with chroot, plus much bit-twiddling. This time, I did the twiddling, and made a reusable tarball, so that I won't have to fuss with that anymore.

      According to the feedback that I have been getting from many GNU-Darwin users, there are still people out there that need this kind of freedom to effectively get things done. I made this thing, because I needed it.

      Regards,
      proclus

  27. what's so hard anyways? by MadCow42 · · Score: 1

    Gee, I really don't see what's so hard about most installations on Linux as it is, even without .rpm's or apt-get...

    1) untar
    2) vi README
    3) make test (usually)
    4) make config
    5) make install

    Is that really that hard for joe-user... or will they look at step 2) and panic? "Oh my god, there's instructions... I can't possibly read those and follow them!".

    If you don't like soup, stay out of the kitchen.

    q:]

    MadCow.

    --
    I used to have a sig, but I set it free and it never came back.
    1. Re:what's so hard anyways? by Anonymous Coward · · Score: 0

      make: don't know how to make uninstall. Stop

    2. Re:what's so hard anyways? by Anonymous Coward · · Score: 0

      "Is that really that hard for joe-user... or will they look at step 2) and panic?"

      No, they'll panic at step (4) when the config dies due to a source dependency and step (2) has failed to list alllll those dependencies.

      NOW what? Where do they go for the needed source?..[end of new Linux user, back to WinLand they go..]

    3. Re:what's so hard anyways? by Peaker · · Score: 1

      Why is step 2 there unless you also have to understand a lot of extra technical details about the system and match them to what the README says? And then start getting lots of lots of new packages, that are dependant on.. or not get them, and have it compile anyhow - with some functionality disabled due to lack of some library you didn't know it was beneficial to have..
      Not to mention upgrading this stuff later..
      In other words: a PAIN.
      Use Ports or apt-get, they really make things easier.

    4. Re:what's so hard anyways? by vs · · Score: 1

      The most important part is
      6) pkg_delete foo.

      You missed
      3.5) Grab FreeBSD-patches (like adding #include before :-/),
      too.

    5. Re:what's so hard anyways? by proclus · · Score: 1

      > make: don't know how to make uninstall. Stop

      You forgot "rm -rf ~/usr". ;-}

      Regards,
      proclus

    6. Re:what's so hard anyways? by proclus · · Score: 1

      Try this.

      make deinstall

      Regards,
      proclus

  28. Oh great, a half-assed distro management system. by Anonymous Coward · · Score: 0

    The ports system is in theory a decently good idea, in practice -- it sucks. The problem centers around the lack of an authoratative download area for several older more obscure programs.

    It's great telling it to start and have it make the program you want. But there is nothing more frusterating than telling it to build ghostview and having it run through 20 mirrors before telling you that it can't find the file it's looking for.

    The same goes for running an older version of FreeBSD. Want to try to install a program using the ports directories? Be prepared for it to tell you that it can't find the tarball.

    Thanks, I'll stick to my SRC rpm's.

  29. Gentoo and the Portage Based Linux Distro by Jagasian · · Score: 3, Interesting

    A full Linux distro that utilizes a "BSD Ports" like software management system is already available. The Linux distro is called "Gentoo".

    One use of a Linux distro like Gentoo would be to add a user-friend-idiot-proof OS installer that plug-n-play auto detects everything about your hardware, from the exact CPU type, MB type, memory type, graphics card, sound, etc... and then keep that system specific info in a local database. After this part of the installation, and for the rest of the life of the system, whenever you install ANY application on your system, the software is automatically optimized and compiled for your specific setup. Applications could be optimized for your CPU-type and the amount of RAM that you have. Maybe even your video card and sound card could be taken into consideration. If you don't have a sound card, any references to sound could be compiled out of the application. If your video card only supports 256 colors, then perhaps, the desired application could automatically be optimized for such a platform.

    This would allow application developers to program with a greater assumed knowledge of the end user's system, and it would make it easier for the end user to have a totally tweaked out Linux setup, apps and all! Not to mention the fact that the Gentoo Portage system deals with dependencies automatically, furthur easing end user headaches.

    Closed source simply couldn't compete with such a Linux distro because closed source software (Windows for example) is compiled for the average hardware setup, which sacrifices performance for generality, while a Gentoo based Linux Distro could automatically reconfigure itself to tighly fit your exact hardware setup, which keeps generality and great performance.

    1. Re:Gentoo and the Portage Based Linux Distro by polarbear · · Score: 1

      I think it would be a good idea to point out that the GUI and autodetection system doesn't exist but the framework does exist and is part of portage.

      Portage is a distribution building engine... it would actually be a great idea if someone wrote the GUI/hardware detection wizard... all it would have to do is just modify /etc/make.conf and the portage profile and tell portage to do its thing.

      --
      --- polarbear
  30. Re:Veering slightly OT - the curbside cowboys by killmenow · · Score: 1

    If RMS keeps this up, some anal types will start compiling alternates for all the GNU utils...
    I am considering doing precisely this. I have started working on a DIY Linux distro a la linuxfromscratch.org only replacing all GNU tools with available alternatives (just to prove it can be done). I have only just begun and am a long way away from having anything remotely usable as I'm just not sure where to find the alternatives...starting with gcc. Anyone?
  31. /usr/src is not at the same level as ports by polarbear · · Score: 1

    Hmmm... slashdot seemed to have eaten my first reply so here goes...

    /usr/src != "in ports"

    In gentoo's portage _every_ component of your system is a proper package thats part of portage. Through the use of portage's profile system _you_ can define which specific versions of which packages you want installed and considered to be "core". By editing a couple text files you can create your own profile where you define what is in the distribution. Portage is more then just a package management system, it can be used as a distribution creation system. Of course you don't need to worry about this if you don't, just use our default profile and you won't need to worry about any of this.

    With portage you are not tied to any specific version of something considered core. We simply define a default profile that we believe is stable and "supported". The end user can go ahead and install gcc 3.0.x and try to build an entire system with it if he wants, its up to the user.

    Once portage stabilizes (we are on 1.0_rc6 right now) distribution releases will be defined by just a few files in a profile directory. In a single portage tree you will have all the files required to build multiple releases of our distribution, the power of the profile system. If you have an existing install and want to upgrade to our current version you just change a single symlink and do a "emerge system" and it will update the packages we defined as being core. Nothing else is changed, etc.

    Hope this gives you some idea why I might get a little touchy when someone tries to compare the seperation of /usr/src + buildworld and ports to the power of portage. :)

    --
    --- polarbear
  32. Increased Cooperation Is Good For Both Camps by Lethyos · · Score: 3, Interesting
    Amusing as the infighting between the *BSD and Linux camps may be, it's hardly beneficial in our primary struggle to wrench market share away from MS. By developing projects that aid greatly in bringing these two platforms together, we can demonstrate a number of things:

    Demonstrate strong interoperability but still have a choice what OS you want to run (*BSD, Linux, MacOSX, etc).

    Increase availability of all kinds of software and toolkits between almost all of the anti-MS players.

    Accellerate development for both platforms by encouraging developers to optimize their software for both camps.

    Now this is a lot to say for such a rudimentary project (and I'm sure the list could go on), but the ideals are there. Imagine if we had increased/improved interoperability between the KDE and GNOME projects (instead of a lot of bitching about the other "sucking ass"). Say, tools that helped unify the appearance of widgets, code sharing layers, and so on.

    So, wordiness aside, unity is good. :)

    --
    Why bother.
    1. Re:Increased Cooperation Is Good For Both Camps by Anonymous Coward · · Score: 0
      it's hardly beneficial in our primary struggle to wrench market share away from MS
      Perhaps the primary goal of Linuxers is that, but it certainly is not the goal of the BSDers (not that we mind about MS)
    2. Re:Increased Cooperation Is Good For Both Camps by JDizzy · · Score: 1

      I'd like to point out to you that we FreeBSD folks do not hate windows, and don't really care to displace it with FreeBSD. So when you say "it's hardly beneficial in our primary struggle to wrench market share away from MS", you must be speaking from a linux centric point of view. The main thing I have to teach people in the linux community is that Linux People tend to be the ones that hate Windows, whereas the FReeBSD folks tend to love unix. Besides, FreeBSD is intended for the server role, not the "replace windows on your desktop" role. If you want to talk about the merits of why we love unix... that is another story...

      -J

      --
      It isn't a lie if you belive it.
    3. Re:Increased Cooperation Is Good For Both Camps by Mad+Marlin · · Score: 1
      it's hardly beneficial in our primary struggle to wrench market share away from MS

      I know it may be hard for you to believe, but I don't care to wrench market share away from anybody. I don't hate Microsoft, I don't hate Windows (although it does get annoying at times, and I avoid using it whenever possible) and no, I don't even hate Bill Gates. I didn't even feel the need to spell Microsoft as mickey$oft. Linux is for people who hate Windows, BSD is for people who love UNIX.

    4. Re:Increased Cooperation Is Good For Both Camps by Anonymous Coward · · Score: 0
      The primary goal of GNU/Linux is freedom for the users. Displacement of Microsoft and other proprietary vendors is jsut a side effect; some even see it as regrettable.

      *BSD users don't accept copylefted software (their treatment of GCC is inconsistent but unsurprising) and their licenses are unsafe--using them would risk subsidizing the same opponents of Free Software we're competing with!

    5. Re:Increased Cooperation Is Good For Both Camps by Anonymous Coward · · Score: 0

      Wrong. The primary goal of the GNU/FSF is to take away a programmer's ability to be payed for their work. Whether they put it in those terms or not is irrelevant, since it is the end result that counts. As a programmer and writer I strongly oppose the FSF's goals.

    6. Re:Increased Cooperation Is Good For Both Camps by Anonymous Coward · · Score: 0

      Work for hire. You don't have to pay for software development by punishing anyone who might have a use for it, and the amount of work you're compensating us for is unrelated to the number of people who want it.

    7. Re:Increased Cooperation Is Good For Both Camps by Anonymous Coward · · Score: 0
      GNU is for people who love freedom so much they donate labor to ensure every user has it; BSD is for people who love Microsoft (and all the other proprietary vendors) so much they donate labor to subsidize more inferior noninteroperable proprietary software and similar customer lock-in tactics.

      Linux is somewhere in the middle--some people view it as a convenient way to get a GNU system, others would cheerfully run Microsoft Linux (now with Shared Source[tm], just not for you) if someone told them it was 1337.

    8. Re:Increased Cooperation Is Good For Both Camps by Anonymous Coward · · Score: 0
      FreeBSD is intended for the server role, not the "replace windows on your desktop" role

      "I once preached peaceful coexistence with Windows. You may laugh at my expense--I deserve it."
      --Jean-Louis Gassee, CEO, Be Inc.

      If we don't take the desktop, we'll survive in server rooms just long enough for Microsoft to find the right level of interoperability problems to make everyone give up and rent XP.

  33. Great! by motadine · · Score: 1

    First, let me congratulate the dedicated people behind this. Yes well done. You have taken an free OS to port it to another free OS.

    But,

    *puts on flame proof suit*

    What does this change? From what I have heard, the software in FreeBSD is hard to use, lame, feature poor, etc..

    What does this change in the world of lets say 99% of desktop users? Yes, I know that people here love Linux, and love seeing application being ported on the platform.

    But is this innovative? Or just reinventing the wheel in a brilliant but useless way?

    The collective Linux brains should be coding something to convert the Windoze through sheer abundance of feature.

    You have heard this before. Make it simple. I am smart. But not everyone is. As much as I love going into Mandrake to do thing, it is all too true. Linux is still an obstacle to productivity for average people.

    Does FreeBSD change this? Somehow I don't think so.

    Aiming for new features, innovation and simplicity. The architecture of Linux is well capable of handling these.

    And yes I am leaving my flame proof suit on..

    --
    Taking on space
    1. Re:Great! by Anonymous Coward · · Score: 0

      "What does this change? From what I have heard, the software in FreeBSD is hard to use, lame, feature poor, etc.."
      wrong. install FreeBSD and see for yourself. basically, it's like slackware but better. you won't notice many differences - i use XMMS, KDE, licq, perl, gcc, etc. just like in Linux.
      those who say that "the software in FreeBSD is hard to use, lame, feature poor" either don't know anything about FreeBSD, or they think the same of Linux.
      the ports system (think of a "port" as a "portal" to an application, not a "port of" an application) is amazing. yes, for source installs (which is what i prefer) it's even better than apt-get.

    2. Re:Great! by Phroggy · · Score: 1

      Damn I'm bored.

      First, let me congratulate the dedicated people behind this. Yes well done. You have taken an free OS to port it to another free OS.

      No, they took a feature of a free OS, and ported it to another free OS that didn't have that feature.

      What does this change? From what I have heard, the software in FreeBSD is hard to use, lame, feature poor, etc..

      The people you heard that from were probably idiots. I can't think of another explanation offhand.

      What does this change in the world of lets say 99% of desktop users? Yes, I know that people here love Linux, and love seeing application being ported on the platform.

      It allows Linux users to use the FreeBSD ports system to install software. If you don't know what that does or how it works, just say so.

      But is this innovative? Or just reinventing the wheel in a brilliant but useless way?

      I'd say porting anything is not innovative, just by definition. They obviously haven't invented anything new here. That doesn't mean it's useless, though - I'm sure once it becomes more mainstream, many people will find it very useful.

      The collective Linux brains should be coding something to convert the Windoze through sheer abundance of feature.

      Who are you to say what the "collective Linux brains" should be doing? These are people with free time who want to do something useful that they'll use themselves, not employees in a company doing what their boss tells them. Your sentence didn't make sense anyway.

      You have heard this before. Make it simple. I am smart. But not everyone is. As much as I love going into Mandrake to do thing, it is all too true. Linux is still an obstacle to productivity for average people.

      You're obviously not as smart as you think you are. The whole point of the ports system is to make things simpler than they otherwise would be, so average people can use it.

      Does FreeBSD change this? Somehow I don't think so.

      Somehow I don't think you'd know one way or the other.

      Aiming for new features, innovation and simplicity. The architecture of Linux is well capable of handling these.

      ...which is exactly why they ported the BSD Ports system (which is a new feature to Linux, and is simple) to that Linux architecture you seem to like.

      Thanks for trolling, have a nice day.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    3. Re:Great! by Anonymous Coward · · Score: 0

      think on the bright side, at least these people are finding ways of staying busy and not developing another mandrake-like OS.

    4. Re:Great! by Anonymous Coward · · Score: 0

      Well said, couldn't agree with you more..

      I should also mention myself, that the poster who wrote that is oviously an idiot user himself.. Well, guess I didn't need to say that as it's more than ovious to all.

    5. Re:Great! by Pierre · · Score: 1

      hehe good move putting on the flame proof suit

  34. I've been using GNU/Linux since 0.48x by FreeUser · · Score: 2

    I've been using GNU/Linux since Linux Version 0.48. Yes, this was around six months after the release of 0.1 and yes, when RMS came it with his "you should rename Linux Lignux" I was as angry, and as vocal, as everyone else.

    He has said that his reaction (a natural one, after all at the time he and his project had written almost all of the software we were using, outside of the kernel itself and the X Window System for those few lucky enough to have it working on their hardware at the time) was a mistake, and if he had it to do over again he would have handled it differently.

    The FSF's stance on wanting the entire operating system to be called GNU/Linux rather than Linux is that they wish to emphesize the Freedom that the FSF philosophy tries to promote, and that recognition for their (by any measure massive) contribution to Linux, or GNU/Linux if you prefer, is very secondary to that goal.

    I have tried to make a habit of refering to the entire collection of software as GNU/Linux not out of some misguided notion of political correctness or to appease RMS as such, but simply as a small courtesy in saying "thanks" to the guys whose software (GNU gcc, file-utils, lib-utils, etc.) and kernel (Linux) has vastly improved the quality of that portion of my life spent in front of a computer and has enabled me to make a very comfortable living. It seems a small request on their part, and the least I can do to give something back.

    --
    The Future of Human Evolution: Autonomy
    1. Re:I've been using GNU/Linux since 0.48x by Anonymous Coward · · Score: 0

      I usually "say thanks" to the folks who provide me with software by paying them money.

      It works at the grocery store too. Just about everywhere I go I can use money to "say thanks" to those who provide me with something.

    2. Re:I've been using GNU/Linux since 0.48x by DrXym · · Score: 2
      I have tried to make a habit of refering to the entire collection of software as GNU/Linux not out of some misguided notion of political correctness or to appease RMS as such, but simply as a small courtesy in saying "thanks" to the guys whose software...


      And by doing so you're being discourteous to all the other guys who wrote stuff that you make a living from. I speak of such stuff as the kernel, XFree86, Perl, Mozilla, Python, tcl, KDE, Apache, Samba, MySql, openssh, webmin, and many more besides.


      FSF software is what it is - a valuable subset of any distribution, but certainly not *so* important that it deserves everything to be tarred with the same brush.

    3. Re:I've been using GNU/Linux since 0.48x by rking · · Score: 1

      And by doing so you're being discourteous to all the other guys who wrote stuff that you make a living from. I speak of such stuff as the kernel, XFree86, Perl, Mozilla, Python, tcl, KDE, Apache, Samba, MySql, openssh, webmin, and many more besides.

      Not really, because they don't seem to care. His point, if I understood correctly, was that he feels that he has reason to show gratitude to the FSF and the FSF have expressed the wish that he call the system GNU/Linux, so he does so. I don't think the other projects you referred to have any desire to be recognised by those means so there is no ingratitude implicit in treating them differently.

      I generally call the system "Linux" myself, it's shorter, simpler, and most importantly has name recognition. I'd just as happily call it GNU if that had the name recognition instead, but it doesn't.

    4. Re:I've been using GNU/Linux since 0.48x by Anonymous Coward · · Score: 0

      It works at the grocery store too. Just about everywhere I go I can use money to "say thanks" to those who provide me with something.

      If that is the only way you know of thanking people then I really do pity you.

    5. Re:I've been using GNU/Linux since 0.48x by Anonymous Coward · · Score: 0

      If you can get everything you want without using money at all then I envy you.

  35. Rebuttal by drodver · · Score: 1
    They're pre-compiled, like debs, but the pkg_add software is terrible! In order to update a package you have to first remove the package then add it again! And if the package has dependancies you have to remove all the dependancies and re-install them all again!

    The whole point of OpenBSD is that is security oriented. Its this way so you know exactly what's changing on the machine. A dependency that is automatically changed might induce security holes, for example. By doing it this way you can investigate and verify that the software is secure before putting it on the system. So what you want is fine on normal linux boxes but for something you are counting on being secure it isn't so hot.

    Plus you can't just do a "pkg_add foo," you have to do a "pkg_add ftp://ftp.openbsd.org{blabalbla}/foo-3.17-2.pkg," which means you not only have to know where to get the file, you also have to know the version number and all other information in the filename in advance!

    The solution is trivial, ftp the package to your drive, then type pkg_add foo{tab}. All done!
    1. Re:Rebuttal by Electrum · · Score: 1
      The solution is trivial, ftp the package to your drive, then type pkg_add foo{tab}. All done!

      But the point is that with Debian, you don't need to FTP it manually. If I want to install Apache, I just type "apt-get install apache". Having to log into the FTP server, find the file and download it, or open a web browser and look around on a page takes a lot longer.

      Don't get me wrong. I have used FreeBSD for the past year at work and I love being able to compile stuff from ports with custom options (although with Debian, there are packages avaiable for most common options). But compiling takes a long time, especially on slower hardware. Building the minimal X libraries to install PHP with GD can take several hours. Being able to "apt-get install php-gd" is very nice. If you could combine apt with the port's system of making it easy to compile things custom and build packages, you'd have the perfect packaging system.

    2. Re:Rebuttal by funky+womble · · Score: 1

      For FreeBSD packages, you can do something like: pkg_add -r wget. No version number or url required.

  36. Interesting by flynn_nrg · · Score: 1

    Thanks for the info, I'll have a deeper look at gentoo when I have the time. Might be a nice option if I want to install a linux box, sound pretty customizable, just if it would be possible to install it with XFS it would be perfect for me.

  37. BSD/Linux by Tony-A · · Score: 1

    Hmmm, interesting.
    What's a poor worm to do?
    OT, but why does OpenBSD have command recall and tab completion in ftp and not in sh?

    1. Re:BSD/Linux by Mad+Marlin · · Score: 1
      why does OpenBSD have command recall and tab completion in ftp and not in sh?

      The shell sh does not have command recall and tab completion, even in Linux. However, the shells bash, ksh, zsh, and many others do. The standard POSIX shell is very simplistic, but there is no reason you must keep using it. Change your shell to something else, which, if you are mainly used to Linux instead of BSD, would probably be bash. I personally prefer zsh.

    2. Re:BSD/Linux by Tony-A · · Score: 1

      Yeah, about the first thing I do in OpenBSD is
      ftp> get bash "|pkg_add -v -"
      and edit /etc/shells
      Also is very nice for seeing what went by on the screen too fast.

    3. Re:BSD/Linux by Tony-A · · Score: 1

      Arggh
      ftp> get bash (tab-completion works here) "| pkg_add -v -"

  38. Problems with Ports by bhsx · · Score: 1

    OK, so i've never used ports before, and i'm trying to 'make install' in a few /games directories, and it continually gives this error...

    $ make install

    Makefile:42: *** missing separator. Stop.

    Anyone know what i am doing wrong? is there something i'm missing, or is this not ready for prime-time?

    --
    put the what in the where?
    1. Re:Problems with Ports by Anonymous Coward · · Score: 0

      Try using gmake.

    2. Re:Problems with Ports by proclus · · Score: 1

      • Makefile:42: *** missing separator. Stop.

      This means that you invoking GNU Make instead of the BSD Make that is
      provided with the ports tarball in ~/usr/bin. Make sure that ~/usr/bin
      comes before /usr/bin in your $PATH
      variable.

  39. It's the apps, dude! by Ungrounded+Lightning · · Score: 2

    Install FreeBSD if that's what you want.

    Forget GNU. Forget Linux. Forget BSD. Forget Microsoft.

    Just use the system that best fits your needs. This may mean that your pet OS is not a universal fit for someone else.


    That's what this is ABOUT!

    The OS and the applications are separate entities. This is a port of the applications so they'll compile and run identically, from a common source base, on both BSDs and Linux. This makes them tweakable on Linux or a BSD, and so on.

    Once this is fully done you'll be able to have a common environment across the (unix-like) OS spectrum. Pull out the OS and swap in another, and it won't matter. So you'll be able to pick or change the OS to meet your needs for *OS* performance, hackability, or special feature set, without having to switch to a different set of applications just because you changed the platform under them.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  40. Re:Veering slightly OT - the curbside cowboys by Amon+Re · · Score: 1

    Dude, don't waste your time.

  41. If you like BSD ports try Gentoo linux by Anonymous Coward · · Score: 0

    Subjet says it all. The Gentoo distro. is not finnished yet but it is inspired buy the BSD ports system. I have it installed on 3 machines so far and it is sweet.

  42. ;) by sir_nas · · Score: 1
    http://www.nasland.nu/officexp.png


    no, not really ;P

  43. Re:Non-GNU Linux by killmenow · · Score: 1

    Dude, don't waste your time.
    Consider it a learning experiment. As long as I learn something, it's not a waste of time. There may be better USES of my time, but that doesn't make it as bad as watching NASCAR.
  44. GUI to BSD ports by Anonymous Coward · · Score: 0

    What I actually use to access the ports in FreeBSD is pib. Pib is a TCL/TK front end to the ports collection. It is point and click for building and installing.

    But what makes pib more usefull is the search. (What programs depend on gtk or what versions of gtk are there.) Or if I can't remember what a program is called I can search the descriptions. (Things that use ghostscript.)

  45. Re:Veering slightly OT - the curbside cowboys by bgarcia · · Score: 1
    I'm just not sure where to find the alternatives...starting with gcc.
    There is no free alternative to gcc. The closest you're going to find is bcc. It is a 16-bit x86 compiler, used by the folks attempting a port to that hardware (the ELKS project). It is only a C compiler, and it has no optimizing capabilities.
    --
    I'm a leaf on the wind. Watch how I soar.
  46. Re:OpenBSD packaging by Tony-A · · Score: 2, Informative

    ftp> get foo "|pkg_add -v -"
    The trick is to do pkg_add inside of ftp instead of ftp inside of pkg_add.

  47. Re:Veering slightly OT - the curbside cowboys by Arandir · · Score: 2

    Let me correct you slightly. KDE, Gnome, MySQL, etc, are NOT part of the operating system. Neither is gcc, bash or emacs. Think about it, if you replaced bash with tcsh, are you now running a different operating system? Of course not!

    An operating system is "software that controls the operation of a computer and directs the processing of programs (as by assigning storage space in memory and controlling input and output functions)." A strict reductionist would consider only the kernel and kernel modules to be the operating system. In reality, we must also include the file system, init process, boot loader, etc. as part of the OS.

    What is there of GNU that is absolutely necessary to get a Linux system up and running? Nothing! However, GNU has provided a mass of software that makes using Linux much, much more convenient. Although this software is not the operating system, it does comprise the majority of the standard Unix "operating environment". Since it is not necessary, I cannot consider it part of the operating system.

    What RMS does not realize in his crusade to rename LinuxOS, is that Linux is a NEW kind of system. It is the first component operating system and environment. It was created not from scratch, but from existing parts. Some of these parts came from GNU, but not all of them. Just as Home Depot does not get to name your kitchen extension, neither does GNU get to name this new kind of system just because it used some GNU parts.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  48. Anything you untar, I can apt-get better. by displague · · Score: 2, Interesting

    I agree..

    I don't know about the rest of the world, but I don't have the disk space, the processor power, and the time to compile everything that I can currently just get from the Debian archives with apt-get. I can try and trash software relatively thoughtlessly.

    I used to play things the build-your-own linux way. I have also used *BSD enough to understand the joy of ports when compared to the build-your-own method.

    Perhaps this would be more of an issue once a "bad-guy" makes his way into the Debian Maintainership and gets a package out there that sends everyone's encryption keys off to Osama Bin Ladin Land (the Terrorist Place on Earth ). But then again, do you check every line of source before compiling?

    --
    Marques Johansson
    1. Re:Anything you untar, I can apt-get better. by Anonymous Coward · · Score: 0

      The beauty part is

      if you prefer installing from source, perhaps because you want to change some compile time options, you may do so, with ports.

      On FreeBSD (I assume on any other system that uses the ports system fully and exclusively), you can _also_ install precompiled binary packages (ala .deb, .rpm, etc) if you don't need any special options or you don't have the required space, or time, etc etc, with the package tools pkg_add, pkg_delete, pkg_info etc.

      From the pkg_add man page:
      -rUse the remote fetching feature. This will determine the appropriate obj format and release and then fetch and install the package.

      (as a former Debian user, this sounds very similar to apt-get)

      _Both_ methods are covered under the same package management system, for the most flexibility possible.

  49. Open Packages is *MORE* than BSD by mr · · Score: 3, Informative

    If you actually LOOK at what OpenPackages is doing, not only does it work with the BSD's, some of the 190+ linux versions, but also with AIX, HP/UX and other Unix platforms.

    OpenPackages is a universal solution. GNU-Darwin is less than universal.

    Depends on what you want. To be inclusive or exclusive.

    --
    If it was said on slashdot, it MUST be true!
    1. Re:Open Packages is *MORE* than BSD by Anonymous Coward · · Score: 0

      Linux fragmentation, gawd damn it sux ass so bad that it's not even worth using Linux anymore.. .Just too many *non-standard* Linux crap distro's... I'll stick to a real UNIX/UNIX Based OS thank you very much, not some over hyped amateurish, patches on top of patches OS, er.. *Kernel*

    2. Re:Open Packages is *MORE* than BSD by proclus · · Score: 1

      > OpenPackages is a universal solution. GNU-Darwin is less than universal.

      Ports = 6000 ready applications
      OP = 1 test application

      Anything else?

      Don't get me wrong, because OP is a great idea. When it is ready, we will merge or pull off some other miracle ;-}.

      Regards,
      proclus

  50. Just run FreeBSD by Anonymous Coward · · Score: 0

    Why bother with Linux at all? BSD was the original and still the best.

  51. You could always.... by phatlipmojo · · Score: 1

    ...install FreeBSD and find out.
    I'm really glad to see this. I'm not l33+ enough (nor am I possessed of the resolve to become so) for some of the FreeBSD fundamentals (making my plug n play pci sound card work, for example--by all accounts not a terribly hard thing to do, but I just don't have the background to understand the instructions I found or the time and patience to learn it. Incidentally, this may be irrelevant by now, as I stopped using FreeBSD a little over a year ago). What I do know is this: the FreeBSD ports collection is the bomb. No joke. As is the installer. I found the installation to be easier than most linux installs (especially the nasty gui ones *coughmandrakecough*).
    Here's the thing: you just heard me admit to not having the chops to make a fucking soundcard work. Now, that said, the ports collection is *easy*. That said, it is also *powerful*. Once I wrapped my head around the idea that ports would actually do what it does (i.e. not take up much space, be easy to use, go get the source, compile it for your system, and install it, complete with all dependencies), my non-sound-worthy ass was installing all manner of stuff with ease.
    In fact, my exposure to the FreeBSD ports collection was the main reason I found Linux distasteful, and have avoided using it. If I could get something that would figure out my damned sound card by itself and work out of the box (like Linux) with the astonishingly easy and powerful ports system, I would be in non-l33+-but-reasonably-competent-end-user heaven.

    --

    Nice things are nicer than nasty ones.
    1. Re:You could always.... by skbenolkin · · Score: 1

      From FreeBSD-4.3 release notes:
      When sound modules are built, one can now load all the drivers and infrastructure by "kldload snd".

      They are all klds (modules) now. Good news for you, perhaps?

      --
      "Frederick, is God dead?" --Sojourner Truth
  52. Re:Veering slightly OT - the curbside cowboys by Mad+Marlin · · Score: 1
    ... unfair to single out GNU/FSF/RMS when KDE, Gnome, XFree, MySQL, sendmail.org/Eric Allman, the ReiserFS, Emacs and LVM people and loads of others ...

    KDE is GNU GPL, Gnome is GNU GPL, Emacs is the main way GNU got started (I believe Stallman wrote much of it himself) as back in the day GNU-Emacs was the first GNU thing to show up on your average commercial UNIX systems. A good portion of the stuff that isn't GNU is GNU GPL licenced, and I would not be suprised if greater than 85% of the code in your average Linux distribution is GNU GPL licenced. However, The GNU GPL nowhere states that the words ``GNU'', ``GPL'', or even ``g'' (i.e., gcc for cc) must appear in the title of the program or system.

    With a statement a bit more on topic, I use FreeBSD mostly, and the ports system is one of the best advantages of FreeBSD over Linux. I will be very happy when I can just type cd /usr/ports/databases/postgresql7; make install on a Linux machine and have PostgreSQL installed when I come back. I hope Red Hat picks up the idea, since that seems to be the main Linux distribution I have to deal with.

  53. seriously reconsider by neutralstone · · Score: 1

    it doesn't matter that it can be done; it's prohibitively expensive. Please inform me if you find an ISO compliant && free C/C++ compiler --I've looked and can't find one. If you've ever seen the language specs in dead-tree form, this will come as no surprise. the process of design and implementation was so huge and complex that it literally required a team of geniuses for it to be realized. Repeating the FSF's efforts just because RMS gets silly about the color of a doghouse is illogical even by human standards.

    If you really want to learn about it, read through the source for GCC & binutils.

    relevant quote from a CS professor:
    "Let this be your mantra whenever you write software: 'Don't re-invent the wheel. Steal it.'"

    1. Re:seriously reconsider by killmenow · · Score: 1

      Repeating the FSF's efforts just because RMS gets silly about the color of a doghouse is illogical even by human standards.
      I wouldn't do it to spite RMS et. al., only as a learning experience.

      I am not talking about writing an alternative to gcc. If there is none, I guess I'm done. My thought was more, if there are alternative tools to the GNU tools, what would it take to make a desktop OS environment devoid of GNU tools. That is an interesting thought experiment. First, having an alternative to gcc would be necessary because so many tools require it to compile (XFree86, KDE, etc.). But even if I could use alternatives to gcc and glibc like Comeau C/C++ and Dinkumware's libraries (not free), I could then get down to tweaking anything else to compile and have an environment that functions for me that is also devoid of GNU tools. Not that I want to do it that badly, I just find it an intriguing idea especially for the learning value.
      Don't re-invent the wheel. Steal it.
      I heartily disagree. I am a proponent of not re-inventing the wheel when working on practical for-production projects. But this is different. I mean, isn't re-inventing precisely what Linus Torvalds did when he decided to write his kernel, what Kurt Skauen did when he decided to develop AtheOS, what RMS did when he decided to make all the GNU tools?

      Lots of things are re-invented by people who are eager to learn how things work and this is not a bad thing...just, as I have said, not the BEST use of my time.
    2. Re:seriously reconsider by Anonymous Coward · · Score: 0

      GNU software re-invented the wheel because RMS wanted software licensed under terms he liked. You can't avoid re-inventing the wheel when said owner of said wheel said you can't use it.

  54. What happens when you had new hardware? by Kahlua · · Score: 1

    but all the support for it's been compiled out of every bit of software on your system? Recompile everything?

    Idiot.

    1. Re:What happens when you had new hardware? by Anonymous Coward · · Score: 0

      Hey fuck you. Someone's thinking about what would be good to add to a system, rather than just criticizing others.

      Do you think Linux got to where it is by saying "Why would anyone want to do anything other than the Windows Way(tm)"?

      Idiot.

    2. Re:What happens when you had new hardware? by Jagasian · · Score: 2

      Most desktop PCs and workstation have relatively static hardware configurations. Even gamers, who change their systems more frequently than others, keep roughly the same hardware for at least 6 months.

      So yes, if you change your hardware configuration on a daily or even weekly basis, such a distro wouldn't fit your needs, but if you are the typical desktop/workstation user, then having your system re-optimize itself whenever you change the hardware, would be a tolerable cost for improved day to day performance. Tolerable because it is very infrequent yet yeilds long-term gains.

      In addition, it wouldn't take much to have the system compile to a certain optimization level. High levels compile the code to exactly fit only the current hardware configuration, while low optimization levels compile towards a more general hardware configuration set, to which your current configuration belongs. That way you can optimize towards maybe just your CPU type and RAM capacity, if you frequently swap out sound cards and video cards (or whatever), and when you keep an entirely static setup, you have the optimizer spend an entire night tweaking the software for your system.

  55. Why Ports is Better by pHDNgell · · Score: 1

    Many years ago, I installed Redhat on my Alpha at work. I went on to install some of the basic packages I use daily, but most of them were not available for Alpha in binary form. This is where ports wins big...the same OS on multiple platforms.

    I'm a huge NetBSD fan, myself. Go look at how many platforms it runs on and you'll see why this makes sense. As a software developer, I only have to, for the most part, try my application on one system and it's available to all. Sure, I can write something that's big endian specific, or won't run in 64-bit mode, but then each one of those problems can be fixed and portability is restored, in one place.

    I've been amazed at how well this has worked out on my multiple NetBSD platforms at home. If it could do the same for multiple operating systems, that would be great for everyone.

    Even on a single machine, it gives you a great deal of flexibility. For example, I don't update my pkgsrc and ports trees, I just get them out of AFS on demand from public AFS servers that update them periodically. Now, even if I did have write access to the AFS servers for building, that'd be slow an irresponsible, so I have it build everything in a tmp directory. Don't like where it installs things? Tell it to install third-part packages somewhere else (such as a platform-specific AFS volume). Got a lot of the identical machines? ``make package'' will make a binary package you can install in a platform-specific directory rather than you having to do the same fetches and builds in multiple places.

    It's a powerful system, and will hopefully get more people looking at systems other than Linux on a PC. Maybe next time I try Linux on an Alpha, or some other hardware, I won't feel so alienated.

    --
    -- The world is watching America, and America is watching TV.
  56. That's Linux you twit. by Anonymous Coward · · Score: 0

    How about freedome to call your shit what you want to and not have the FSF try and rename it for you?

    If they really want freedom, if they really want to give their shit away, they gotta live with people doing shit with it they don't like.

    RMS has his own kernel, Hurd, it he had gotten it out less the 5 years after anouncing it we wouldn't be having this discussion, 'cuz Linux wouldn't have needed to write his kernel to begin with. RMS and the FSF need to just deal ans shut the fuck up.

    1. Re:That's Linux you twit. by Anonymous Coward · · Score: 0

      And they do. Nobody's proposing a license change that would require you to be honest about what software you're running, just as you aren't required to work on improving the software.

      If you find a bunch of Corvette parts laying around (which is no coincidence--the people who cast the parts want people making Corvettes, and that's exactly what the parts are there for), assemble them, add your own gearbox, and drive away, you're rightly going to have trouble convincing anyone that what you're driving somehow fails to be a Corvette.

      Since you've benefitted from the work going into Project GNU, you have an ethical obligation (but not a legal one) to support it. Not hiding its existence from our peers (many of whom still believe Linus wrote all the important code by himself) is the very least you could do.

  57. dude by ArchieBunker · · Score: 0

    what kind of linux nazi are you? vi is the last thing I'd use to view a readme. Ever heard of the more command?

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  58. Ports is a different kind of distrabution. by Kaiser+Sose · · Score: 1

    Right now the ports tree is not akin to any of the Linux distrobution models.

    FreeBSD (as w/ other BSD) has the advantage of having a single distribution, so packages listed in ports can contain distro specific patches. Hence, all the work going into FreeBSD weather it be the Base system or the apps is compounded togeter in a central repository.

    Linux is not so lucky. The different linux distibutions all have different file heirarchys (yah, there are "standards" . . but that doesnt mean they're followed). Each distribution also has it's own package distribution method. This is a problem for ports.

    On my FreeBSD system, ports allows me to grap the source, add my own optomization and other compile/configure time flags, and have the perfect package. It doesn't just randmly install the stuff, it packages it up first (see pkg-plist file), and then installs it. This is great, because weather you choose to use the binary package, or the port, there's no dependency problems.

    If you install the Linux-Ports on your Debian/Redhat/Mandrake system, and install something, and later try to install an official package, your going to have dependency problems. You'll be forced to install the "official" version of the program, and you lose the advantage of ports.

    Even if the Linux-Ports stuff was able to detect your distro, build the appropriate type of package, and then install it, you've strayed from the central distro chain. Debian (apt), RedHat (up2date), and Mandrake (I dunno what it's called) have their own centralized package systems, and will detect that your package differs from the latest one on the server. Your ports package gets overwritten, and your screwed again.

    Ports would be great for Linux, but I dont think it will happen unless some distro decides to add it to their standard distro . . . Long live FreeBSD.

    --
    "All that we see and seem is but a dream within a dream." --Edgar Allen Poe
  59. Bit more to it by Pierre · · Score: 1

    The use of ports isn't as simple as getting a particular program running on your box.

    For FreeBSD the ports tree is a very nice way for maintainers to modify the packages, via patches, to handle differences in the system software. I'm not sure of all of the differences but when making low level system calls surely the Linux/BSD kernels have special requirements. The ports tree allows maintainers to insure that software follows system policies on security etc. as well.

    If you just want to download binaries all the time you wouldn't be any more interested in the ports system than you would be in building your own RPMS or DEBs.

    Updating software using the ports system is, I think, where it shines. You can keep your ports system up to date using cvs. If a package get's updated you can use a utility called portupgrade to get the new source/patch it/compile it/upgrade it.
    You just have to type something like %portupgrade greatprogram.

    Since everything is compiled on your system you don't have to deal with dependencies as much. Anybody who has tried installing the latest KDE rpms on a redhat system might appreciate this.

    So it's more like an automagic way to build and install the latest rpms/debs/pkg for your computer.

    Having said that, it's just a matter of preference.

  60. Correction by killmenow · · Score: 1

    My thought was more, if there are alternative tools to the GNU tools, what would it take to make a desktop OS environment devoid of GNU tools.
    Meant to write:

    My thought was more: if there are alternative tools to the GNU tools, what would it take to make a desktop OS environment devoid of GNU tools...but still using the Linux kernel?

  61. Here is the solution... by Mekanix · · Score: 1

    Just call it XFree86PerlMozillaPythontclKDEApacheSambaMySqlopen sshwebminGNU/Linux

    1. Re:Here is the solution... by Anonymous Coward · · Score: 0

      Why does XFree86 get to be first? Perl is much more important to Linux than some X Windows system...

  62. Best of Both Worlds by Anonymous Coward · · Score: 0

    Slackware + BSD ports = recompile kernel + compile applications = Best of Both Worlds.

  63. Re:Veering slightly OT - the curbside cowboys by Arker · · Score: 2

    I understand RMS' point here, but a Linux distro is much more than just Linus' kernel and a bunch of GNU stuff on top. It seems unfair to single out GNU/FSF/RMS when KDE, Gnome, XFree, MySQL, sendmail.org/Eric Allman, the ReiserFS, Emacs and LVM people and loads of others are just as well-deserved of a honourable mention.

    Silly silly. Emacs is GNU - in fact it was the first piece of GNU. Gnome is GNU also. But that's not the point.


    The point is that an Operating System is a collection of software that makes a computer usable. There is a minimum level, and it's more than a kernel. You have to have a text editor. You have to have a compiler collection. Without those you can't do anything at all.


    RMS and the FSF have been working to make all the crucial components of an OS available for decades. Without that work there wouldn't be any Linux. Don't believe me? Just what do you suppose Thorvalds himself had to have before he started writing the kernel? VIM and GCC. RMS himself wrote GCC. VIM was written by people inspired by his example, who preferred the design of vi, but longed for the freedom of Emacs.


    For that matter, BSD in the form we know it today relies on GCC, and quite a bit of other GNU software too. It's probably possible, at this point, to put together a Free system that doesn't use anything GNU. But it would be an inferior system, so no one, not even OBSD (Theo hates RMS and yanks anything GPL out of his base the moment anything half-usable under another license is available,) does. But would it be possible to do that at this point if it weren't for RMS' unflagging uncompromising belief in Free Software, were it not for the tremendous amount of work he has done? I very much doubt it. So yes, I think he does deserve some credit, and yes, I think it's quite accurate to call most linux-based OSes GNU/Linux.


    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  64. MacOSX? by Sanity · · Score: 1, Troll
    I don't see why you consider MacOSX to be worthy of our support. Apple has historically demonstrated a willingness to lock people in to proprietary hardware and software that makes Microsoft look positively reserved. Just because they have largely failed in this regard, should not earn them any respect. Yes, they have built OSX on-top of an Open Source platform, but OSX remains closed-source.


    I don't think "not being Microsoft" is a sufficient criteria for the support of the Open Source community.

    1. Re:MacOSX? by proclus · · Score: 1

      This means that GNU-Darwin is free software built on an open source platform. What's the problem?

      Regards,
      proclus

  65. Re:Veering slightly OT - the curbside cowboys by Amazing+Quantum+Man · · Score: 2

    So the OS is Linux, and the whole could be referred to as the "GNU/Linux Environment", as Kernighan and Pike once referred to the "Unix Programming Environment"...

    --
    Fascism starts when the efficiency of the government becomes more important than the rights of the people.
  66. Re:Veering slightly OT - the curbside cowboys by joshv · · Score: 1

    Trust nobody with a 6-digit user id

    Trust nobody with a with 16-digit user id (binary representation)

    -josh

  67. Re:Veering slightly OT - the curbside cowboys by jerdenn · · Score: 2

    The point is that an Operating System is a collection of software that makes a computer usable. There is a minimum level, and it's more than a kernel. You have to have a text editor. You have to have a compiler collection. Without those you can't do anything at all.

    Actually, an operating system does not need a text editor, etc. - spend some time in the embedded world.

    -jerdenn

  68. Excuse me by Arker · · Score: 1

    Excuse me, I meant an operating system for a general purpose computer. I did expect that much to be understood. Obviously if you're computer is designed to run a watch or something, things are different. You still have to have a text editor and a compiler on the general purpose computer you use to set the thing up though.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:Excuse me by Anonymous Coward · · Score: 0

      Soldering irons and logic probes are all I need.

      We are talking about our fetishes here, right?..

    2. Re:Excuse me by killmenow · · Score: 1

      You still have to have a text editor and a compiler on the general purpose computer you use to set the thing up though.
      Compilers are not necessary for a general purpose computer. They are often necessary to Linux and *BSD users who can't always get what they want pre-compiled...but you can install many Linux distros without gcc/egcs and still have a highly functional general purpose computer...same can be said for all Windows platforms, OS/2, Mac OSes, etc. The compiler is an option, not a necessity.
    3. Re:Excuse me by Erik+Hollensbe · · Score: 1

      Without a compiler, there would be no applications to run on the operating system. The fact is, is that someone, SOMEWHERE, has to have a compiler so that you can run your application.

      Granted, I don't think this has anything to do with the fact that GNU/Linux should be called GNU/Linux. The basic toolset and libraries that are required run the system should be the reasons it's called GNU/Linux.

  69. You've missed his point by A+nonymous+Coward · · Score: 2

    I don't waste time calling it GNU/Linux either, but at least I understand his point. It's not the amoount of software involved, it's the fact that it uses the GPL, and that the FSF was *the* pioneer in enforcing free software (as opposed to open source).

    So many people continue to harp on how other software makes a bigger part of any distro that I can only assume that they have blinders on and do not want to admit that he has a point, at least from his point of view. I think they just want to bash RMS and the hell with needing a valid reason.

    1. Re:You've missed his point by Reality+Master+101 · · Score: 1

      ...I can only assume that they have blinders on and do not want to admit that he has a point, at least from his point of view...

      RMS always has a point "from his point of view". The question is whether he has a point from a reasonable/sane person's point of view.

      It's not the amoount of software involved, it's the fact that it uses the GPL, and that the FSF was *the* pioneer in enforcing free software (as opposed to open source).

      Even if I accept that GPL software is more "free" than other open source software (which I don't, it is clearly more restrictive therefore less free), I don't accept that every piece of GPL software has to pay homage to the FSF. If someone wants to do voluntarily give credit, that's fine, but it's pretty damn arrogant of RMS to insist on it.

      I think they just want to bash RMS and the hell with needing a valid reason.

      As they say, "as ye sow, so shall ye reap" or to put it another way, "what goes around comes around". RMS brings it on himself. You have to give him credit for giving a lot to his cause, but you also have to condemn him for damaging his cause. What's interesting about RMS is that clearly he is an intelligent guy, but he also seemingly is incapable of figuring out how to stop shooting himself in the foot.

      Well, I can recognize his particular brand of genius, while also recognizing his particular brand of absolute, braindead stupidity.

      --
      Sometimes it's best to just let stupid people be stupid.
    2. Re:You've missed his point by Nugget94M · · Score: 2

      Is it just me, or does anyone else find it deliciously ironic that out of one side of RMS's mouth he complains bitterly about people who refuse to accept his mandate on renaming "Linux" to "GNU/Linux" while also objecting to the old BSD advertising clause?

      RMS and the FSF at one time objected to the BSD license for a clause that existed in the BSD license which required people who incorporated BSD code to include credit in any related advertising or documentation.

      Personally, I think it's a lot less objectionable to be required to give credit to a resource in an advertisement than it is to giv the FSF authority to rename my projects at their discretion.

      How is this any different than the advertising clause which RMS denounced?

  70. Re:Veering slightly OT - the curbside cowboys by Arandir · · Score: 2

    Actually, for many distros, I would just call it the "GNU Environment", as that's what it is. (and coming from me, that's saying a lot).

    You could very accurately describe a Linux distro as "The Linux operating system plus complete GNU environment, XFree86, KDE, GNOME, etc."

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  71. ...and then there was one by jgsfcaus · · Score: 1

    This one thread probably reflects the state of the OS wars better than any other. Its amazing how similar these battles are in relationship to what is happening with mainstream religions (by religion I mean the organized dogma created by humans who share similar thoughts of spirituality, something entirely different.)

    We all know how similar most protestant religions are. Some of the major ones (at least in the US) have recognized this too and have decided to merge (or re-merge, as they may have once been unified in the past) The thought is that perhaps it is not important how each one intreprets some arcane symbolism and which intrepretation is better. What is important is that they both have essentially the same message and the same goal. (Forgive my oversimplication of this, and sorry if I don't even remember what the names of the two religions are that I referred to earlier.)

    Likewise with the various flavors of what is essentially Unix. You've all mentioned what your favorite method of software distribution is and have stated why this is so. Perhaps someday you'll see how pointless it is to bicker about the subtle differences and you'll work towards a common goal of reunifying the factions into a cohesive force which will probably be called Unix. Through this process, perhaps you will learn how similar it is and that by only focusing on the differences, you are forgetting your common goal and your original message. Quite frankly, I don't know what your message is, because I am relatively new to this world, having dabbled with these wickedly time consuming things we call computers since appx. 1980. I can say one thing: those working on the UI aspect of *nix seem to have a more clearly stated goal and have more successfully avoided the traps of constant infighting that seems typical of you plumbing guys. You could learn from them.

    So, in some ways, these discussions are one way to essentially recognize that what makes you different is actually what makes you similar, and therein lies your power. Just don't lose sight of your common goal, whatever it might be.

    More to the point of this discussion, I have probably dabbled with everything that has been discussed here. My most successful experiment as been Gentoo Linux, but that's only because I took the time to actually read the instructions on what to do, and was able to overcome the incredibly stupid mistakes that were made in the documentation that so many have stated isn't rocket science. Rocket science is useless if the rocket you build can't get off the ground. What good is it if you end up putting wheels on it and use it to drive from San Francisco to LA?

    Debian's apt-get is fabulous but quite frankly the whole Debian thing reminds me too much of Scientology. No, actually it reminds me more of Amway. Of course apt-get is simple and the only way because that is what you get with Debian. No negativity here. You agreed to the Debian Social Contract, and therefore you must abide by that agreement. There is no other way.

    Conectiva Linux has to be the best distribution to co-opt the structured order of Debian with the freewheeling rpm methodology. I think it is closes to realizing that you can have your cake and eat it too. Naturally, if there is a way to override rpm's safeguards, then don't give some poor new user such hell because they forced a package in. Afterall, you gave them the tool to do it by leaving in a back door. Conectiva has probably figured out that human nature is what it is, so help them by giving a bit more order to their "sin." The alternative is frustration on the users part, so why not just realize that to sin IS the norm and people will be people. I think what they have done is said there are more ways to achieve the same thing, and most users don't give a crap about any of them. They just want the end result, no sermon, no dogma, no eternal pain and suffering. Just give them what they want with minimum frustration and be happy that their systems are still stable and functional. Let them have the goddess, just call her Mary and incorporate her into your dogma. Let them have their midwinter rituals and their multiple deities. Just split your one diety into three different ones (God the father, God the son, and God the holy ghost). There is room for all of it, but always remember why you are here and not there. Otherwise, you won't be anywhere pretty quickly.

    Sorry, this message has meandered everywhere across the map and often off of it entirely. But, I also want to take a minute to thank each and every one of you. This entire movement, whether you call it the FSF, GNU/Linux, KDE, Gnome, whatever. I am in awe of the energy and talent that has brought you this far in such a short time. No company can possibly ever hope to accomplish this in the same manner. Let it be both a compliement and warning to you that IBM and other biggies have recognized this. Just remember: the devil knows the bible frontwards and backwards.

    My hats off to all of you. Keep those flames agoin and keep the fire hot!

    Jack Greenwood
    San Francisco

    --
    Jack Greenwood Southern California Inland Empire Suburban Hell
  72. GGOKTHXBYE by mrRaist- · · Score: 1

    Way to to Linux. Just one more thign that you've ripped off from FreeBSD... Good job!

    1. Re:GGOKTHXBYE by Anonymous Coward · · Score: 0

      you're a fucking retard

  73. GNU/DARWIN is BSD, not Linux! by Anonymous Coward · · Score: 0

    Folks, this has nothing to DO with Linux.
    (or even GNU/Linux). Darwin is the BSD kernel used by MacOS X.

    So, basically, the article says that GNU/Darwin now has a ports tree, modelled after FreeBSD's.

    The headline is WRONG.

    1. Re:GNU/DARWIN is BSD, not Linux! by proclus · · Score: 1

      Hey man, I wrote that headline, and I'm the founder of GNU-Darwin and a longtime GNU/Linux person. What-the-heck is wrong the headline?

      What is GNU/Darwin?

      Regards,
      proclus

  74. I always wondered... by Adrian+Voinea · · Score: 1

    Who the hell is this RMS guy and what does GNU mean anyways?

  75. I'm sure we all agree, but about Linux... by Anonymous Coward · · Score: 0

    I definitely agree, nice to see more propagation of the *nix species :) I have used both apt get and ports/pkg systems, and am satisfied with either, my only complaint is directed at Linux in general, and that is all of the "linux-centric" apps floating around now, hell, I can barely d/load anything it seems anymore without some strange proc or libc.soxxxx or not found error or whatever the case may be....however must about anything else works on most of the unices, it mostly Linux that seems to want to be different. If you think about it, kinda makes linux users sound like MS, eh? At least in the sense of doing things "their way" only. Anyhoo...

  76. yep, Chill is right by Anonymous Coward · · Score: 0

    about 8 hrs, even on a dual 233Mhz Intel (and same on my pIII400), but I do remember before the great wave of newbies to Linux that users were always screaming "but you don't want precompiled binaries, just get the source d00dz" and even now, almost daily at /. I see "hrrmmmppphffff, harddisk space is a nonissue these days" and the linux users toss that excuse around too...it just seems to me that Linux users keep changing their lines of reasoning to fit the argument, that's all.

  77. gnu darwin by Anonymous Coward · · Score: 0

    I'm still trying to figure out why anyone cares about gnu darwin. GNU/linux, sure, the gnu folks stepped in and made a unix system available under their license. But Darwin? Darwin is a custom unix designed and built by one company for their own usage. What's next? GNU/AIX? GNU/Solaris?

    1. Re:gnu darwin by Anonymous Coward · · Score: 0

      >Darwin is a custom unix designed and built by one company for their own usage

      It's FreeBSD w/mach you dumb shit.

    2. Re:gnu darwin by proclus · · Score: 1

      GNU-Darwin is free software built on an open source OS. We have thousands of users. Any more questions?

      Regards,
      proclus

  78. note to Lyenux kiddi3s by Anonymous Coward · · Score: 0

    we know, after all, we were doing this long before you wet-behind-the-ears gen-x'ers came along, now isn't it past your bedtime sonny? oh yeah...+5 for that? wow, there's no bias at /. eh?

    1. Re:note to Lyenux kiddi3s by DrXym · · Score: 2
      As I've been using Linux for nearly a decade and contributed thousands of lines of code, I think I am qualified to express my opinions on the matter.


      Perhaps anonymous pricks like you had actually contributed code yourself then you might compehend why people take offence at the FSF claiming credit for their work. That is what calling it GNU/Linux is tantamount to.

  79. weak excuses by Anonymous Coward · · Score: 0

    real tough to "vi Makefile" and comment out the line "broken=" eh? here's a hint, use a # before broken, fool, then you can install it and play with it, and the only broken one I've seen lately (that's even useful) is Mozilla. Remember, Linux lusers used to whine all day about "NEVER install precompiled binaries, heavens no!!! get the source !!! " and now look at you all..tsk tsk hypocrites, well you can keep apt. We don't want you in bsdland, nor your "mob rules" style of programming. Ugghh

  80. (Offtopic, -1) (Philosophy, +1) by kubrick · · Score: 1

    In the beginner's mind there are many possibilities. In the expert's mind there are few. --Suzuki-roshi

    So being certain and closed mined makes one an expert? I don't like that quote at all!


    Who wants to be an expert? I think what this means is that we should all cultivate the open-mindedness that a beginner brings to a problem, and be prepared to consider concepts that are outside our experience.

    I've also heard it expressed as "The more you learn, the less you know."

    Maybe it should read In the young mind there are many possibilities. In the elderly mind there are few.

    Ageist! :)

    --
    deus does not exist but if he does
  81. I'm only gonna say this once by scrytch · · Score: 3, Informative

    so listen up. Ports has nothing to do with "porting" software from one platform to another. The ports collection is basically a package management and browsing system. It's a directory of packages, broken into categories, like ports/games, ports/net, ports/security, and so on. Each package has a makefile. The makefile will download, compile, create and install a binary package for that package and every one of its dependencies. It differs from traditional package managers in that dependencies are not done by package, e.g. kde doesn't look for a package for qt, it looks for the proper version of libqt.so -- think of it like a sort of autoconf. this saves you from the dependency hells other package managers put you through, and if you install a dependency manually, then things still install (and if you screwed up the dependency, well, that's your problem). When it's finished installing, the source tree sticks around (until you do a make clean), so if you need to modify something for your local system, you can go into the source, tweak at will, then make install again.

    gentoo uses something very much like ports, though it doesn't use make, but a python utility called emerge instead. i would hope to see it use SCons in the future, and get the best of both worlds -- it might even be enough to get me to switch back to linux (once it stops having a VM bug of the week)

    --
    I've finally had it: until slashdot gets article moderation, I am not coming back.
  82. hmm... by Anonymous Coward · · Score: 0

    It's a bit curious how your original post contains phrases like "which is working towards their 1.0 release" and "Definatly check them out" - implying you are merely a satisifed user of the distro, with no stake in its success.

    However, in the above post you slipped and said "we are on 1.0_rc6 right now", which suggests you are a little more involved with the project than you let on to originally.

    I have to ask, is it really necessary to fake grass-roots support like that? If your product is any good, it will speak for itself.

    1. Re:hmm... by polarbear · · Score: 1

      I didn't mean to "fake grass roots support". I'm just some minor developer among many. Gentoo wasn't my idea and I didn't write portage. I've just contributed ebuilds (aka portage packages) and support.

      In the future I'll watch my grammar as I don't want to alarm the conspiracy freaks and possibly any BSD zealots who might be offended that something like Gentoo exists (not that I'm accusing you of either) ;)

      --
      --- polarbear
    2. Re:hmm... by Anonymous Coward · · Score: 0

      Thanks for clearing that up - the impartial viewpoint seems justifed in that case. No harm meant. :)

      I actually intend to try gentoo "one of these days" - and not just because it's the only distro out there (that I'm aware of, at least) that ships with a program I've written. :) Come to think of it, drobbins himself reported a bug in the aforementioned program once upon a time - very nice fellow.

  83. Re:Veering slightly OT - the curbside cowboys by richie2000 · · Score: 1
    Formally and technically, you are of course correct. However, the naming issue is more one of marketing and as such Linux has become the name that encompasses not only the original Linus kernel and modules, but entire distributions and bundled application packages. Windows is still Windows if you remove Minesweeper (albeit its usefullness just shrunk by 50%) but people still think of Minesweeper as part of the Windows bundle/offering/package/distro/whatever - not to mention Office, without which Windows would be an empty shell with very little market share. Office can not be said to be a part of the Windows OS by any technical standards, but it IS a crucial part of the MS/Windows marketing machine.

    So, what's in a name? Whatever we bundle in it.

    --
    Money for nothing, pix for free
  84. Re:Veering slightly OT - the curbside cowboys by richie2000 · · Score: 1

    Sure, but that name wouldn't go over well when the CNN anchor tries to report the news that the "OS formerly known as Linux" has surpassed Windows in installed user base a few years from now, now would it? :-)

    --
    Money for nothing, pix for free
  85. Re:Veering slightly OT - the curbside cowboys by Arandir · · Score: 2

    No, but it's something to put on the front of the box to make RMS happy. Oh wait, nothing makes RMS happy...

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  86. wonder if this'll get bsd more attention by bwhalen · · Score: 1

    As a longtime bsd user, I am glad to see the os get a little attention this way. The dependency system is quite nice and easy.

    --
    Where do you want to be, What are you doing to get there.
  87. Re:Veering slightly OT - the curbside cowboys by Erik+Hollensbe · · Score: 1

    I think the major point here is that without the GNU toolset (just about everything in /bin and /sbin, and a good portion of /lib too), there would be no Linux OS, just a kernel. If someone decides to port the vast quanitity of FreeBSD tools to Linux, then I think that would make a bit more sense.

    I have several systems that do not have XFree86, Samba, etc on the machines. All of them carry the basic GNU tools, regardless if they have a compiler or not.

    Granted, I think that GNU/Linux would be better treated as a 'formal' name, and not expected to always be referred to as that name. eg, WinME vs Windows Millenium Edition.

  88. Mod this up please by XNormal · · Score: 1

    Moderate this post up, ok?

    --
    Stop worrying about the risks of nuclear power and start worrying about the risks of not using nuclear power.
  89. so you're the one using all the printf's still eh? by Anonymous Coward · · Score: 0

    and just contributing to the thrown-togetherness of the whole linux experience? lovely.

  90. Re:Veering slightly OT - the curbside cowboys by NutscrapeSucks · · Score: 1

    An operating system is "software that controls the operation of a computer and directs the processing of programs (as by assigning storage space in memory and controlling input and output functions)."

    Well, you'd have to have your head in an hole to be ignorant of the more common definition of "things that come on the CD with what is formally defined as an operating system". This is the definition that's far more relevant to everyone not writing a computer science textbook.

    Even the GNU GPL uses the term "operating system" in this sense (calling a compiler a "major component" of the OS) and that's the legal document that allows the whole thing to be shipped.

    Personally, I think the concept of a "distribution" or "operating environment" is marketing claptrap that hinges on an obscure technical point, but is designed to obscure the incompatibilities between different Linux-based OSes. Calling the different OSes themselves "Linux" (as Linus allows) is also a little white lie.

    --
    Whenever I hear the word 'Innovation', I reach for my pistol.
  91. Unfair by Anonymous Coward · · Score: 0

    How come, if we get a [+1 FUNNY] moderator selection, we don't also get a [-1 NOT FUNNY] selection? Seems like a real oversight to me.