Slashdot Mirror


Debian NetBSD

bXTr writes "Interesting project over at SourceForge. Quoting from the website, 'Debian NetBSD is a port of the Debian Operating System to the NetBSD kernel. It is currently in an early stage of development and cannot currently be installed from scratch. Instead, a tarball of the current envionment is available and can be extracted into a handy directory on a NetBSD system.' Check out the reasons why they're doing it and some interesting commentary at DailyDaemonNews on this."

346 comments

  1. kaboom by magicslax · · Score: 1

    Two open source minorities combine in a brilliant flash of light Because we can. .

    1. Re:kaboom by erlenic · · Score: 3, Insightful

      To me this kind of thing really shows the strength of the open source community. I'm sure we've all seen the flame wars that start here over the difference in the licenses, but in the end, we all have a common goal, share the source!

    2. Re:kaboom by Anonymous Coward · · Score: 1, Insightful

      It's not so much a common goal, as it is compatable goals.

    3. Re:kaboom by Anonymous Coward · · Score: 0

      I'd like to see something like this done with Darwin, and eventually OSX (they are different to an extent). This would allow a wider audiance to use OSX and still feel at home.

      Just my $0.02

    4. Re:kaboom by Anonymous Coward · · Score: 0

      This is *news*???!!!

      Taco, you seriously need a life man...

    5. Re:kaboom by mAIsE · · Score: 0

      http://fink.sourceforge.net/

      works great for me so far in OS-X

    6. Re:kaboom by Anonymous Coward · · Score: 0

      Fink is for program compatability. Each Linuz distro has it's own feel and set up, the uselands very a great deal.

      What the post is about is porting the Debian distro to the NetBSD kernel. This would alow people who are used to useing Debian on Linux to migrate to NetBSD based systems with a much much msaller learning curve, little to none. So, you can see how this would be beneficial to OSX. It would allow Linux geeks, and not just FreeBSD geeks to migrate to OSX and fell at home.

    7. Re:kaboom by mAIsE · · Score: 0

      fink is the debian tools, apt-get dselect etc... about 270 packages currently (its been out about 3 months). It also has startup dameons for compatibility that are not included in OS_X / Darwin.

      I use Xfree86 almost daily and it was installed on my OS_X workstation via Fink automatically.

      It is definitely not a Debian emulation layer but all the ports are managed through the debian tools for OS_X and as a Debian user on i386 hardware it makes maintaining, upgrading and installing a dream on OS-X.

    8. Re:kaboom by Anonymous Coward · · Score: 0

      Thank you for all of that info, it's much appretiated.

  2. Eh... why not? by 1155 · · Score: 1

    I don't see why not, we have lindows, and now deb-bsd, so it shouldn't be bad.

    1. Re:Eh... why not? by jsprat · · Score: 1

      Don't forget debian-cygwin

      Debian on Windows!

  3. debian netbsd port by ralian · · Score: 1

    I thought NetBSD's motto was to port to anything and everything with a CPU (viz. NetBSD Dreamcast), not to get another operating system ported to it ;)

    Disclaimer: Yes, yes, I know what they did and it's not porting an OS. I just found it sort of funny, in a 'tables-have-been-turned' sort of way.

    --

    -raph

  4. I would prefer the other way around by horster · · Score: 5, Informative

    personally, I would like to see a BSD distro with ports and all, but with a linux kernel.

    I just installed FreeBSD recently and have to say i was blown away with how professional the installer was, very simple and powerful - not to mention the ports system.
    debian is nice, apt-get is a great program and the net install is awesome, but I can't say I have much love for dselect. I think debian shows the most promise of any linux distro right now, but in terms of polish, I have to give it to FreeBSD so far.

    1. Re:I would prefer the other way around by legend · · Score: 1

      What is wrong with the FreeBSD kernel?

      I have been in no situation where the linux kernel is better than the FreeBSD kernel.

      --
      If you can't figure out my address, just drop me an e-mail and I will explain.
    2. Re:I would prefer the other way around by horster · · Score: 2, Interesting

      not so much what's wrong with the FreeBSD kernel as what's wrong with linux user land. I would like to see the FreeBSD installer & ports system, to begin with, exist on a linux distro.
      I'm new to FreeBSD, so I might be wrong, but it seems like linux gets more of the new 'sexier' things. sambafs was on linux first, numa, IBM s/390 port - those kinds of things. not to mention binary support, which ok, there's linux emulation in FreeBSD, but it's easier to do it straight on linux.

    3. Re:I would prefer the other way around by King+of+the+World · · Score: 0
      I have been in no situation where the linux kernel is better than the FreeBSD kernel.
      Congratulations, but that's only a comment that you don't use SMP.
    4. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      Yeah, Linux's SMP support is great. It's a shame that the VM subsystem is broken and crashes the kernel regularly. I had high hopes for Linux, too.

    5. Re:I would prefer the other way around by horster · · Score: 2, Informative

      dude, chill out, I'm not dissing bsd!
      binary support means I can run jdk1.3 natively without any emulation layer.
      more drivers (like nvidia) are things that I do use on linux, and as for the rest, no they are not things that I need, but a possible reason why some one would choose linux over FreeBSD.

      there is no need to start a flame fest here - both BSD and linux have their respective advantages.

    6. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      Does FreeBSD have anything like Video4Linux? (e.g. can I watch TV, capture, etc?)

    7. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      My brooktree runs better on FreeBSD than sputtering Linux.

    8. Re:I would prefer the other way around by aussersterne · · Score: 3, Insightful

      What is wrong with the FreeBSD kernel?

      FreeBSD doesn't have as many drivers for esoteric hardware. Not a technical advantage for Linux so much as a side effect of the greater market penetration.

      But that's the way it is, nevertheless.

      --
      STOP . AMERICA . NOW
    9. Re:I would prefer the other way around by ignorant_newbie · · Score: 1

      why a linux kernel? i mean, the FreeBSD kernel is older, more stable, offers Linux (and SCO) binary compatability... the only area it's slighty worse than Linux at is SMP, and on an Intel system this is pretty worthless anyway.

    10. Re:I would prefer the other way around by cymen · · Score: 2

      I'm with you. Personally I would use a well done distrib that had the linux kernel + a base system and ports. I would also still use FreeBSD. Why do people have such a hard time seeing the benefit here? The linux kernel + base system + ports would be awesome for my laptop, desktop, etc. FreeBSD would be humming away on my servers. Of course if I started to really like the linux system better my servers might go that way too eventually but I don't see how either side would be affected negatively by a well done linux distrib that had these features.

      Of course I'm not going to spend the time to make it. Talk is cheap :).

    11. Re:I would prefer the other way around by cymen · · Score: 2

      Intel system this is pretty worthless anyway.

      Uh... Hrm... Mind trying to justify such a position? If it is worthless why is there such an effort in the FreeBSD community to make SMP priority for 5.0? Argue the point if you must but at least make sense :).

    12. Re:I would prefer the other way around by Dahan · · Score: 3, Funny
      personally, I would like to see a BSD distro with ports and all, but with a linux kernel.

      Me too, but only to annoy the FSF zealots who keep insisting on GNU/this and GNU/that :) LinuxBSD would be funny--nothing GNU except for the toolchain and a few other utilities. I don't actually see a real advantage of a system like that over a standard Linux distro, but the idea amuses me :)

    13. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      BSD forked from UNIX a long time ago. Considering that the people running the current BSD projects intentionally reject things like the Single UNIX Specification, it does not have the right to freeload off of the UNIX name. Linux is much closer to UNIX than any current version of BSD.

    14. Re:I would prefer the other way around by psamuels · · Score: 2
      LinuxBSD would be funny--nothing GNU except for the toolchain and a few other utilities. I don't actually see a real advantage of a system like that over a standard Linux distro, but the idea amuses me :)

      David Parsons created a distro a few years ago with pretty much exactly this in mind. Parsons on the GNU utilities: "Unfortunately, these tools come with a few albatrosses around their neck: FSF bloat, FSF philosophy, and Richard Stallman." One of his goals was to minimise the amount of GPL code in his distro.

      It's called Mastodon Linux.

      --
      "How can you claim that you are anti-crack, while still writing a window manager?" — Metacity README
    15. Re:I would prefer the other way around by Free+Bird · · Score: 1

      The BSD projects reject the Single UNIX Specification because many BSD things are just plain better than their SystemV equivalents. There is no point in reducing the quality of your software just to comply with a lame standard.

    16. Re:I would prefer the other way around by haggar · · Score: 1

      You don't give -any- arguments why you would prefere the Linux kernel! Well, of course, Linux ZEALOTS don't need any arguments, Linux is just better, it's the 11th commandement, I guess.

      As far as I can tell, the jury is still out on the verdict whether the Linux kernel is better than FreeBSD. FreeBSD has some threading and messaging capabilities that Linux lacks.

      --
      Sigged!
    17. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      eh?

      FreeBSD's packaging sucks in comparison with debian. OTOH, the performance is great - it feels much more solid than linux, right from the start. I would *LOVE* to see debian on a freebsd kernel, and if NetBSD is similar, then yea.. that'll do.

    18. Re:I would prefer the other way around by Anonymous Coward · · Score: 1, Insightful

      Does linux have support for usb mice yet? The last time I tried installing it, it didn't.

    19. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      Yes.

    20. Re:I would prefer the other way around by scrytch · · Score: 2

      Yah, but RMS won't shut up til ya build it all with lcc :^)

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    21. Re:I would prefer the other way around by kan · · Score: 2, Insightful

      IMHO, because if you need high end system in the first place, you will be really better served by buying system from Sun, IBM or HP. Their offerings of enterprise-class systems are much more mature and stable than any of the i386-base alternatives on the market today.

      SMPng project is not only about improving SMP performance of FreeBSD. It is also about making kernel fully preemtable, which has its advantages for real-time tasks, responsiveness in desktop and multgimedia environments. Besides, with an upcoming PPC and UltraSPARC ports having better SMP support kinda starts making more sense :)

    22. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      So why don't you just use BSD?

      You said nothing of the capabilities of the
      Linux kernel, over and above functionality
      in BSD, so I can only assume that you are
      either a zealot, or a victim of brand
      recognition...

    23. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      you can use the apt-get system via a bsd-ports interface if you like, check this out:http://www.debianplanet.org/article.php?sid=27 1

      Also you CAN use apt-get to fetch sources, there dependencies, and compile in swift move (gotta love deb-src)
      Finally the DID state that part of the reason they where doing it was because there ARE linux distros that utilize a BSD posrts system over the linux kernel.check gentoo linux, plus sorcerer linux seems similiar.
      Anyway back to cane field for me :)
      stop

    24. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      err
      http://www.debianplanet.org/article.php?sid=271
      I wish I knew html

    25. Re:I would prefer the other way around by Craig+Davison · · Score: 1

      If I want to mount a share over SMB in freebsd, I'm screwed. There's no sambafs in the kernel.

    26. Re:I would prefer the other way around by cymen · · Score: 1

      IMHO, because if you need high end system in the first place, you will be really better served by buying system from Sun, IBM or HP. Their offerings of enterprise-class systems are much more mature and stable than any of the i386-base alternatives on the market today.

      One could say the same thing about a non-SMP i386-based server versus one of the high end providers. The whole point is that x86 SMP servers raise the bar without raising the prices to those high end provider levels. There might be some drawbacks to x86 SMP but we've all seen people using them for years with various versions of Windows. Obviously other people out there in the *nix world see some value in x86 SMP and are working to make it just another platform choice.

      SMPng project is not only about improving SMP performance of FreeBSD. It is also about making kernel fully preemtable, which has its advantages for real-time tasks, responsiveness in desktop and multgimedia environments. Besides, with an upcoming PPC and UltraSPARC ports having better SMP support kinda starts making more sense :)

      Well yes but it is also to just plain get SMP going well. That is why I don't buy your arguement :). I'm sure you have valid points but neither of your responses highlight any reason that SMP on x86 is worthless and shouldn't be pursued.

    27. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      If FreeBSD was a UNIX, it would be illegal to distribute it.

      You newbies missed the legal battles of the early 90s, and constantly spout stupid bullshit like "FreeBSD is UNIX (tm)."

    28. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      From 4-STABLE release notes:
      (4.5 has release candidates out)

      Version 1.4.3 of the smbfs userland utilities have been imported. smbutil(1) and mount_smbfs(8) are now available in the base system, without the need to install the net/smbfs port. Note that mount_smbfs(8) will automatically load the smbfs.ko module into the kernel, even if LIBMCHAIN and LIBICONV were not compiled into the kernel.

      Note that FreeBSD before this does have smbfs support via the abovementioned port.

    29. Re:I would prefer the other way around by asyncster · · Score: 0

      > Why did *BSD fail
      You sound like it has already failed, which is the opposite. FreeBSD's userbase is steadily increasing. The number of ports is incresing constantly. Not to mention there are more or less 20 daily updates to the system source (in FreeBSD). Is this what you call failing? Every linux user that switches to BSD gets hooked. Try it, and you'll love it.

      > *BSD is fragmented between a myriad of incompatible kernels
      Since when are the kernels supposed to be compatible? FreeBSD, NetBSD, and OpenBSD are all designed for different purposes, and they have different goals.

      I dont know whether you have a broomstick up your ass or you just want to start a OS war. *BSD is by far the most stable OS. Look at the Netcraft uptime surveys, 42/50 of the sites with highest uptimes all have BSD. Does this say something?

      By the way, I don't really see the purpose of this project. Many NetBSD utils are designed specifically with the NetBSD kernel (ipfw, smbfs, etc...). Not to mention most of the /bin and /usr/bin of linux and NetBSD are identical. Basically you will end up with a weird version of NetBSD.

    30. Re:I would prefer the other way around by T-Punkt · · Score: 1

      You can use sharity-light as it`s called now (old name was "rumba"). On NetBSD the package is located in the category "net".

    31. Re:I would prefer the other way around by kan · · Score: 1

      But there is. Since FreeBSD 4.4, if I am not mistaken. And external patches to do just that have existed for at least last two years. No need for sharity-light.

    32. Re:I would prefer the other way around by kan · · Score: 1

      On 2-way SMP machines the performance difference between Linux and FreeBSD in SMP department will be negligible. There were test from Byte magazine published recently, where misconfigured FreeBSD did more than adequate against Linux 2.4 despite the fact that FreeBSD kernel was configured with MAXUSERS value which is way to low for any reasonable use. It is when number of processors is more than two then Linux should start showing advantages. Once you abandon cheap dual-processor market segment, you will find that prices for Intel-based servers are not that different from the same class Sun or IBM boxes.

      >neither of your responses highlight any reason
      >that SMP on x86 is worthless and shouldn't be
      >pursued.
      And I never intended to argue that. I was simply stated that the importance of supporting SMP on i386 is quite overrated.

    33. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      YHBT you stupid shithead

    34. Re:I would prefer the other way around by Pseudonym · · Score: 2

      Quite. Many of us use Linux despite the GNU userland, not because of it.

      Apart from bash, that is. That beats [t]csh any day. The rest I can lose in favour of BSD.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    35. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      If UNIX is lame, that's fine. But why try to identify your product with something that's lame?

    36. Re:I would prefer the other way around by cymen · · Score: 2

      Thank you for clarifying the issue. I do not have any experience with x86 SMP servers with > 2 cpus so I did not think along those lines. I now understand where you are coming from...

    37. Re:I would prefer the other way around by dublin · · Score: 3, Interesting

      personally, I would like to see a BSD distro with ports and all, but with a linux kernel.

      I agree. Although I think the BSD kernel is arguably superior, having a Linux kernel would allow the rapidly increasing number of commercial applications that run on Linux to work.

      The big, ugly, problem for me (and almost anyone else that's really worked with and appreciated the real power of *real* Unix, as opposed to Linux) has always been the GNU utilities. They're acceptable, but just barely. GNU Documentation stinks when iut's there at all, at least partly because even most FSF-backers recognize that man pages are the expected form of OS docs and info pages are a hoppeless GNU-ism.

      The GNU utilities insist on using their own hopelessly convoluted syntax, (especially the hideous "--" options, another perversity enforced by the gnazis that intentionally creates a gulf between the GNU wasteland and the civilization of the Unix/BSD world.

      The BSD utilities are one of the best reasons to run BSD - they are orders of magnitude more stable and standard than their GNU hack counterparts. The code for many of these utilities is indeed old, but has not remained static: The BSD utilities provide a level of maturity that GNU will probably never reach, simply because structure and gols of their organization forces the BSD folks care about such things, while that of GNU seems to ensure that that level of care and attention will not be lavished on the code. In my mind, this is a distinction that is far too often overlooked.

      --
      "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
    38. Re:I would prefer the other way around by Anonymous Coward · · Score: 0

      You just got trolled in a very sad way. You clearly haven't been here long.

  5. Well... by Anonymous Coward · · Score: 1, Flamebait

    At least Enron isn't the only group of people jumping off of sinking ships! About time Debian started moving to an operating system that doesn't have VM problems every other release. Go ahead! Mod this one down!

  6. mirror by Anonymous Coward · · Score: 0, Funny

    for those to lazy to click the link here is what it says:

    Why Debian NetBSD?
    NetBSD runs on hardware unsupported by Linux. Porting Debian to the NetBSD kernel increases the number of platforms that can run a GNU-based operating system.
    The Debian Hurd project demonstrates that Debian is not tied to one specific kernel. However, the Hurd kernel is still relatively immature - a Debian NetBSD system would be usable at a production level.
    Lessons learned from the porting of Debian to NetBSD can be used in porting Debian to other kernels (such as FreeBSD and OpenBSD).
    In contrast to projects like Fink or Debian w32, Debian NetBSD does not exist in order to provide extra software or a Unix-style environment to an existing OS (the *BSD ports trees are already comprehensive, and they unarguably provide a Unix-style environment). Instead, a user or administrator used to a more traditional Debian system should feel comfortable with a Debian NetBSD system immediately and competent in a relatively short period of time.
    Not everybody likes the *BSD ports tree or the *BSD userland (this is a personal preference thing, rather than any sort of comment on quality). Linux distributions have been produced which provide *BSD style ports or a *BSD style userland for those who like the BSD user environment but also wish to use the Linux kernel - Debian NetBSD is the logical reverse of this, allowing people who like the GNU userland or a Linux-style packaging system to use the NetBSD kernel.
    Because we can.

  7. No Complaining by Aknaton · · Score: 0, Flamebait

    NetBSD is under a BSD license. Taking it and putting it under the GPL is no worst then a corporation taking it and making it closed source.

    Plus, it should be interesting how it turns out.

  8. Cooperation by awgy · · Score: 3, Insightful

    To me, this is promising. I like to see cooperation between the Linux world and the *BSD world. Both have their advantages, and it'd be great if both would learn from each other more often. Perhaps this is an instance where some exchange of ideas could come about? Those responsible deserve a pat on the back.

    --
    Kein Mitleid für die Mehrheit.
    1. Re:Cooperation by Anonymous Coward · · Score: 0
      So why now? Why did *BSD fail? Once you get past the fact that *BSD is fragmentd between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. *BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personalities?

      The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD re one step away from spiritualists wishing to communicate with the dead. s the situation grows more desperate for the adherents of this doomed OS, the sorrow tkes hold. An unremitting gloom hangs like a death shround over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.

  9. slashdot is censoring you! (see link) by Anonymous Coward · · Score: 0, Flamebait

    Slashdot is abusing its unlimited mod points to keep censoring this post!

    This might be offtopic, but it is important to do something about it!

    1. Re:slashdot is censoring you! (see link) by Anonymous Coward · · Score: 0

      not offtopic f00

  10. Re:That is why Microsoft gets all the customer bas by p24t · · Score: 1

    Some people truly don't understand the possibilities of things like porting. Or they have no idea what porting is. Porting, in case that is the case, is making software useable to many people on different operating systems and hardware configurations. Say you want to run a program, and you're running Solaris on a SPARC. But the person who originally wrote the program wrote it for Linux, on x86. Its useful, but not to you, since you don't have what it takes to use it. Now someone comes along and ports it to Solaris/SPARC. You can now use that program. Whee!

    That is why Microsoft loses a customer base. Flexability.

    Its also what's great about various *NIX distros. If there's something you don't like about, say Suse (just as an example, I liked Suse) - but like some other things about it. Now someone else comes along with a Suse-based distro, or just another distro altogether, which has more of what you want. Switch. Simple as that. Use whatever you want, however you want. But if you make changes, especially really cool ones, let other people use them, too. That's just being nice.

    Flexability.

  11. How about FreeBSD or OpenBSD ? by mAIsE · · Score: 0

    This is a great step but i would love a dselect and apt-get port for FreeBSD or OpenBSD, Two OS's that i have actually used.

  12. Gentoo linux by metalhed77 · · Score: 4, Informative

    Gentoo Linux has that, www.gentoo.org , it uses a ports style system, i'm not sure if it's a direct port of ports, or their own deal.

    --
    Photos.
    1. Re:Gentoo linux by horster · · Score: 1

      thanks, I'll check that out.

    2. Re:Gentoo linux by Anonymous Coward · · Score: 1, Informative

      I tried gentoo, perhaps someday it will be in the same ballpark as FreeBSD (or even Net/Open), but not now. The install is less than perfect, the portage system currently has very little to choose from. Also, there is no BSD-style separation of base and packages.

      Its a good idea though, I also would love to see BSD-like distro based on a Linux kernel.

    3. Re:Gentoo linux by krogoth · · Score: 2

      What exactly is the ports system? Anyone up for some extra karma? :)

      --

      They that quote Benjamin Franklin on liberty and safety deserve neither.
    4. Re:Gentoo linux by asyncster · · Score: 0

      Well, the ports system is basically an extremely easy way of installing applications. The ports skeleton is in /usr/ports, and it has many sub-directories containing different categories of applications (archivers, ftp, devel, etc...). Just cd to the port you want and type 'make install' and it downloades the sources, even the sources of the dependencies and builds it for you.

      BSD also comes with pkg_add which downloads the binaries from their FTP site and installs without any compiling. This is more useful for extremely large things (XFree86, GNOME, KDE, etc...).

    5. Re:Gentoo linux by cymen · · Score: 4, Informative

      Ports is a collection of applications that can easily be compiled for your operating system. Basically for FreeBSD you have /usr/ports. That directory contains various subdirectories dividing applications into www (apache, mod_php4, etc), lang (ruby, etc), mail (mutt, exim, etc), and so forth. Each directory for a specific application contains a number of files. Some of these are patch files that are applied to the source code of the port. See the ports tree doesn't contain the actual code of the application - it only contains enough logic to get the regular .tar.gz release (usually from the developers home site) and the patches to build it properly (particular distribution preferences on file structure, libraries, etc).

      Every couple days I use cvsup to suck down the modifications to the ports tree to my FreeBSD box. Then I happen to use a relatively new tool not in the base system (portupgrade, written in ruby) to check if my currently installed packages are up to date. If they aren't, I can instruct portupgrade to upgrade them or go to each directory individually and do a "make install". Oh yeah, each directory has a Makefile :).

      It's sort of like why distribute the source code if it is just going to get out of date (plus you'll be getting the source for all kinds of crap you never end up using). Of course now each application must be compiled but if you don't want to do that you can use the packages (precompiled binaries that can be added with pkg_add, etc).

      Another benefit is ports can be on any version of the operating system because it is independent of the base system. Look at RedHat and you'll see compiled packages for RedHat 6.2, 7.2, etc (of course, before someone knee jerks a reply, RPMS are out there but I'm trying to make a point here). Ports avoids this. The price is compilation. A trade off. You make the call.

      Hope that helps. Here is the FreeBSD handbook section for ports: ports-using.html (it contains a better description of what files are in a ports directory).

    6. Re:Gentoo linux by iceburn · · Score: 1

      Gentoo uses their own program which acts like Ports. Its called Portage, and I think its written in Python. Right now they have almost 1200 packages in the /usr/portage tree. Its quite an impressive application. One of the cool things I have noticed is that when you merge the Linux kernel sources, it will also go and get the preemtible kernel patch, the low latency patch, and the XFS stuff, and it'll patch the kernel automatically! It also does a great job of finding dependencies, and you can even specify what a given package should compile in, for instance if you want to merge vim, it will tell you it needs XFree86 (if you don't already have it merged). If you don't want it, you can take X out of the USE variable, and it will compile vim without X. Very flexible.

      --
      A sphincter says what?
  13. Re:Mirror of wonderful post by Anonymous Coward · · Score: 0

    Wow, so Microsoft is worrying about open source software like MySQL because of... um, could someone remind me?

  14. how is it GNU-based if it has a _BSD_ kernel? by horster · · Score: 1

    is it just me or is it terribly pretentious to take the work of the NetBSD team, shove some debian/gnu stuff on top of it and call it a GNU-based operating system?

    1. Re:how is it GNU-based if it has a _BSD_ kernel? by Anonymous Coward · · Score: 0

      If the userland is GNU, it's as much GNU-based as it is NetBSD-based.

    2. Re:how is it GNU-based if it has a _BSD_ kernel? by CatherineCornelius · · Score: 2
      is it just me or is it terribly pretentious to take the work of the NetBSD team, shove some debian/gnu stuff on top of it and call it a GNU-based operating system?

      The beauty of the Debian approach is that sits a GNU system on top of a kernel. Source packages developed for Debian should build and run on any Debian system. The kernel is just a way of getting to the metal.

    3. Re:how is it GNU-based if it has a _BSD_ kernel? by Anonymous Coward · · Score: 0

      Oh quit your whining. NetBSD wouldn't run too well without this: http://cvsweb.netbsd.org/bsdweb.cgi/gnusrc/gnu/

      I really don't see what your problem is. Don't worry, Debian-BSD won't suddenly make NetBSD as popular and mainstream as linux, you won't have to switch OSes again just yet...

    4. Re:how is it GNU-based if it has a _BSD_ kernel? by nomadic · · Score: 2

      I don't see how you can refer to Debian as an "operating system". I mean, they do nice work, but an OS without a kernel is just a bunch of applications and utilities.

    5. Re:how is it GNU-based if it has a _BSD_ kernel? by CatherineCornelius · · Score: 3, Informative
      I don't see how you can refer to Debian as an "operating system". I mean, they do nice work, but an OS without a kernel is just a bunch of applications and utilities.

      That's perfectly correct--the Debian system is aiming to independent of the kernel, so it seems to be developing into a portable userland (not a word I had encountered before, but suddenly everybody seems to be using it!) on top of whatever kernel you like.

      Incidentally I notice that there was some debate on the Debian-BSD list as to whether to use the GNU name here, since unlike HURD they don't have libc6, and it's been argued that many essential parts of Debian aren't GNU anyway. And they might want to give the sysadmin the option of building a more BSD-like system (since the BSD userland is there for that kernel). The consensus so far seems to be Debian NetBSD.

    6. Re:how is it GNU-based if it has a _BSD_ kernel? by ideut · · Score: 1

      Yes. In the olden days computers were so hard that technicians were employed full time to operate them. These technicians were not the people using the computers for research. They were just there to operate the machines. When the operation of the machines became automated, the system that did this was called an "operating system". So you're right, the term operating system is a lot lower level than many people realise. Anything that isn't to do with multiplexing the hardware isn't part of the OS. It's part of the user environment.

      --

      --

    7. Re:how is it GNU-based if it has a _BSD_ kernel? by Fluffy+the+Cat · · Score: 2

      No more so than taking the work of the Linux team, shoving some debian/gnu stuff on top of it and calling it a GNU-based operating system. Linux is GPLed, but it's not part of the GNU project. If the GNU C library was being used, I don't think there'd be any real argument. As it is, I'm not so sure.

    8. Re:how is it GNU-based if it has a _BSD_ kernel? by SpinyNorman · · Score: 2

      Uh, no... Debian sit's a GNU system on top of the GNU glibc library, just the same as any other Linux distribution.

      The glibc library provides the userland interface to the kernel.

    9. Re:how is it GNU-based if it has a _BSD_ kernel? by Anonymous Coward · · Score: 0

      Debian doesn't use glibc???

    10. Re:how is it GNU-based if it has a _BSD_ kernel? by Dahan · · Score: 3, Informative

      Actually, it runs perfectly fine. Nothing in gnusrc is critical, and depending on what you want to use the system for, gnusrc might be completely useless. The only thing GNU I have on my Compaq IA-1 is grep, and it's running NetBSD without any problems at all. If I really wanted to, I could probably ditch grep and replace it with awk to be completely GNU-free. But I deleted the GNU stuff (and a bunch of BSD stuff too) for space reasons, not anti-GNU reasons.

    11. Re:how is it GNU-based if it has a _BSD_ kernel? by Arandir · · Score: 1

      The glibc library provides the userland interface to the kernel.

      Um, no. The *kernel* provides the userland interface to the kernel.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  15. Since 1999 by kenneth_martens · · Score: 2, Informative

    If you check out the mailing list archives, you can see the project has been ongoing (or at least discussed) since May 1999. It just until now to get it to the point where it actually sort of works.

  16. BSD + MySQL + PHP = Crap by Anonymous Coward · · Score: 0

    I don't see any SQL Server or C# errors there. Here comes .Net, something that works!

    1. Re:BSD + MySQL + PHP = Crap by Anonymous Coward · · Score: 0

      Here comes .Net, something that has
      try {
      }
      catch {
      }

      to niceley hide useful error messages and replace
      them with messages that mean nothing to show "you are aware of the problem and it's going to be fixed soon"

    2. Re:BSD + MySQL + PHP = Crap by WildBeast · · Score: 2

      heuh? So does Python.

    3. Re:BSD + MySQL + PHP = Crap by Anonymous Coward · · Score: 0

      I wasn't saying open source languages lack try/catch, I was just criticizing misuse of try/catch to hide useful error messages and replace them with something meaningless.

    4. Re:BSD + MySQL + PHP = Crap by WildBeast · · Score: 2

      true but those error messages are usefull to the developper, not the users. Some error messages will provide usefull information to crackers like a database name, the path to a file, etc. I believe that's why they choose to use try/catch.

  17. Re:Mirror of wonderful post by AnimeFreak · · Score: 1

    Buddy, the MySQL settings are probably set to a low queue limit and since the queue limit is full it is rejecting all incoming connections until a spot is availble.

    I know this from experience. They probably have set it down to a lower level because the system can't handle a higher queue level.

  18. Re:the kernel? my god man by tao · · Score: 4, Informative
    Why on earth why would you want a linux kernel in BSD userland? Do you really want a horribly broken VM system and every yahoo who can type hello world submitting patches? Thats why I like BSD. Theres a core group in charge of what goes and what stays. Who has the final say so in the linux kernel?

    Ever heard of Linus Torvalds? Oh, and for the v2.4 kernel it's Marcelo Tosatti, for v2.2 it's Alan Cox. For v2.0, it's yours truly. It's hardly like anyone can get their code into the kernel. Anyone is free to submit patches though. That doesn't mean it'll get in.

    As for the VM, yes, there have been problems (mostly with corner-cases, though), but v2.0.xx has a stable VM, v2.2.xx has a stable VM now, v2.4.xx has a stable, if somewhat unoptimal VM now, and v2.6 will hopefully have Rik van Riel's VM, which shares a lot of similarities with the VM from FreeBSD, but with some Linux-specific adaptments.

    So please, don't spread FUD.

  19. 2.4.17? by King+of+the+World · · Score: 0

    Is this still true with recent kernels from the (snigger) stable branch?

    1. Re:2.4.17? by Anonymous Coward · · Score: 0

      Yes, it's still quite awful compared to FreeBSD's superb VM and schedule combination. They're still a lot of infighting on kernel development over VM, and neither look particularly pretty. I'm sure they'll figure it out sometime.

  20. You don't understand. by alfredo · · Score: 1

    Because we can is the spirit behind all great or not so great endeavors. You can never tell what might come out of it.

    --
    photosMy Photostream
  21. So how long... by nrc · · Score: 1


    So how long before they declare that we have to start calling it GNU/NetBSD?

    1. Re:So how long... by rjamestaylor · · Score: 2
      • So how long before they declare that we have to start calling it GNU/NetBSD
      How about GNUtBSD, for short?
      --
      -- @rjamestaylor on Ello
    2. Re:So how long... by Anonymous Coward · · Score: 1, Funny

      I don't know, but I can say it will happen before Richard Stallman takes a shower.

  22. gentoo.org not available by horster · · Score: 1

    I wonder if the project is still going.

  23. Debian is not Linux by CatherineCornelius · · Score: 5, Informative
    To me, this is promising. I like to see cooperation between the Linux world and the *BSD world.

    Well I agree with you that it's promising, but do remember that the Debian project is not Linux, but a GNU operating system. There is Debian GNU Linux, and there is Debian GNU HURD, and now (apparently) Debian GNU BSD.

    1. Re:Debian is not Linux by lertl · · Score: 1

      GNU BSD is an oxymoron, isn't it? :-)

    2. Re:Debian is not Linux by SpinyNorman · · Score: 2

      That's true of EVERY Linux distribution - they all pair the GNU libraries (glibc, etc), GNU tools (gcc, etc), with Linux kernel. There's no such thing as a non-GNU Linux system, and I don't think anyone trying to sell a Linux distribution that consisted of Linus's kernel sitting on a CD all alone would get too far! ;-)

    3. Re:Debian is not Linux by efgbr · · Score: 1

      Just a small correction: there's no such thing as GNU Linux. Linux would be called that way if it were a GNU project.

      Instead, use GNU/Linux, GNU/Hurd or GNU/BSD.

    4. Re:Debian is not Linux by Arandir · · Score: 2

      remember that the Debian project is not Linux, but a GNU operating system.

      Bullhockey! The name of the operating system is "Linux". The name of the distribution is "Debian". As the distributor, Debian could call the OS any damn thing they want. They could have called it "Fred", but they chose "GNU/Linux" because that involved the least amount of bloodshed on the Debian mailing lists.

      A few definitions are in order:

      Operating system: "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)" [Merriam Webster]. This specifies a kernel and some bits of surrounding infrastructure (such as a filesystem, init scripts, etc). Everything else is extra. They are not part of the operating system.

      The GNU System: An operating system created as part of the GNU Project. The FSF very clearly refers to GNU as "an operating system". Unfortunately, the FSF doesn't really know what an operating system is. They talk about games and mail clients and all sorts of stuff that aren't part of operating systems. It really seems that they aren't describing an operating system, but an overall collection of software that just happens to include an operating system.

      Until Debian releases "Debian GNU/Hurd" in a finished state, there will be no GNU System.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  24. Re:the kernel? my god man by jelle · · Score: 1

    " Theres a core group in charge of what goes and what stays."

    Actually, in Linux it's the same (f.e. Torvalds, Cox, Tosatti).

    And with BSD carrying the BSD license, anybody can take the code and do anything to the code. And with the freedom the BSD license gives to everybody, the 'takers' don't even have to contribute anything back, not even credits.

    Guess how we ended up with so many different *BSD versions? Yes, the BSD license, and the tight control of the people running some of the BSD projects have created multiple forks already.

    Some people think that all that is good, others think that is bad, which is one of the reasons why there always will be BSD _and_ GNU.

    Personally, I haven't made up my mind about that yet, but I use Linux because it has Debian and interesting developments such as the vservers patch (=jail++).

    Debian for *BSD is a good thing, it will make it easier for Debian-users to give *BSD a try.

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
  25. works for me by metalhed77 · · Score: 1

    works for me

    --
    Photos.
  26. Re:ROFL by tao · · Score: 1

    Grow up. No, the code has not been stolen in any way (and for that matter, using it wouldn't be stealing anyway, because of the license... But that's beside the point.) Rik van Riel has been talking a lot with the FreeBSD VM-wizards, and looked at the FreeBSD code. He has then developed a VM of his own for the Linux-kernel.

    Oh, and it's not like *BSD is totally free from influence from the Linux-kernel... Just face it, the point of open-source is to help eachother out.

  27. hmm by Enrico+Pulatzo · · Score: 1, Funny

    How's that for your hardcore, commie conspiracy?

  28. Try these by Arker · · Score: 4, Informative

    Slackware, the daddy of em all - still alive and kicking. Very BSDish install, similar package handling, BSD init. No ports system last I checked :( but a very friendly system otherwise for compiling from source. http://www.slackware.com

    Gentoo, a newcomer, to oversimplify a little the idea seems to be Slack+Ports. Haven't used it yet, heard some great things, sure looks promising. http://www.gentoo.org

    Also another similar project that was just recently reported here - sorcerer linux. Don't know enough about it to differentiate it from gentoo, the ideas seem very similar unless I'm missing something (quite possible, haven't had the time to try either.) http://sorcerer.wox.org/

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:Try these by horster · · Score: 1

      yeah, right now slack is absolutely my favorite (posting from it on my laptop right now), but I am concerned with the one man show aspect of it, and the silence on the website.

      the lack of a network install was too much of a pain for me last week so I just went ahead and installed freebsd (i lost my copy of slack 8.0 somewhere along the way).

  29. kernel performance by Anonymous Coward · · Score: 0

    Does anyone have any specs on the differences in kernel performance between NetBSD and Linux?

    1. Re:kernel performance by Metrollica · · Score: 0

      Try here

      --



      --Metrollica
    2. Re:kernel performance by someonehasmyname · · Score: 0, Troll

      Off the top of my head NetBSD-stable kernels don't corrupt all dismounting filesystems. Only one linux kernel has so far, but I'm sure there's more to come.

      I don't think Linux was prepared for the mass hysteria surronding linux, and is becoming bored of supervising the kernel.

      --
      Common sense is not so common.
    3. Re:kernel performance by someonehasmyname · · Score: 1

      "I don't think Linux" = "I don't think Linus"

      --
      Common sense is not so common.
  30. Re:That is so exciting *yawn* by The+FooMiester · · Score: 1

    which piece of news do you think is more insignificant ?

    well, what's significant is that we can run NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on NetBSD on Debian on . . . .

    segmentation fault. core dumped.

    Awww, shucks. I was having fun

    --
    The previous has been a secret message to my comrades.
  31. Mac OS X will unify the *BSDs by Anonymous Coward · · Score: 2, Interesting

    Really, the convergence of Debian package management, GNU utils and NetBSD kernel isn't all that special and WILL NOT create a stronger, unified, easy-to-use UNIX variant.



    Please, try Mac OS X; there's every advantage to it without all the traditional UNIX disadvantages.



    • Simplified installation - OS X installs easily
    • Easy-to-use interface - A yummy GUI interface that a first-time user can grok, with an excellent command shell for advanced users.
    • Powerful inexpensive yummy hardware - G4 PowerMacs trump x86 by a long margin and cost much less than underperforming but expensive SPARC, MIPS and the PeeCee user's Holy Grail of DEC Alpha, which was intended to run WinBlows from the beginning and is dying anyways.
    • Best design - look at the new iMac! Complete Apple Goodness from the small footprint to the sharp LCD display, all surrounding a powerful G4 processor.
    • Open Source, even though GNU zealots will not agree. Fellow BSD'ers will soon recognize the errors of their ways and join ranks with the Apple crowd.
    • Mac's ain't PeeCee's ;-)


    My hope is that OS X will unify the BSDs into its proper place - at the top of the OS food chain. Many Free/Open/NetBSD users are coming to that conclusion as are many Linux users, beset with flaky kernels and horrible OS packaging.



    Apple OS X and the *BSDs will be our answer to WinTel/Linux obsolescence.

    1. Re:Mac OS X will unify the *BSDs by Anonymous Coward · · Score: 0

      Just what the world needs. All the BSDs running as the only process on top of Mach.

      What a great idea! Its the best of both worlds! All the bleeding edge performance of a microkernel, with all the fault isolation and modularity of a monolithic kernel!

    2. Re:Mac OS X will unify the *BSDs by CatherineCornelius · · Score: 2
      [MacOs X has] Powerful inexpensive yummy hardware - G4 PowerMacs trump x86 by a long margin and cost much less than underperforming but expensive SPARC, MIPS and the PeeCee user's Holy Grail of DEC Alpha, which was intended to run WinBlows from the beginning and is dying anyways.

      I don't know where you get your hardware from, but it is my experience that the cheapest powerful kit around is Intel-compatible. I'd love one of these Mac boxes, but I just cannot afford one.

      And as for the alpha, it was originally designed by Digital to run its VMS operating system, not Windows, which was at that time a 16-bit shell running on top of MS-DOS.

    3. Re:Mac OS X will unify the *BSDs by Anonymous Coward · · Score: 0
      * Powerful inexpensive yummy hardware - G4 PowerMacs trump x86 by a
      long margin and cost much less than underperforming but expensive
      SPARC, MIPS and the PeeCee user's Holy Grail of DEC Alpha, which
      was intended to run WinBlows from the beginning and is dying
      anyways.


      Get your facts straight: Digital designed Alpha
      to be the RISC successor to their CISC VAX
      architecture. It was intended to run VMS and later
      its OSF/1-based UNIX (Digital UNIX, now Compaq
      Tru64).


      Comparing the Moto G4 to DEC Alpha is nonsense -
      Alpha is 64-bit and *still* holds the lead in
      FP performance over *all* MPUs.


      What's more, Alpha is an exceptionally clean
      RISC architecture, unlike those monstrosities that
      are SPARC and especially PowerPC (which now can
      hardly be considered RISC-like).

    4. Re:Mac OS X will unify the *BSDs by Anonymous Coward · · Score: 0

      You need to study the concepts involved here a little more.

      Mac OS X is NOT OpenSource, and has no relevance in this discussion. Darwin is the OpenSource core you seem to be referring to. That, though, doesn't have the yummy GUI you mention. Furthermore, the reliance on closed mac hardware goes directly against the concepts of openness in platforms. Darwin's ability to run on non-mac machines is still non-existant, and I suspect that Darwin was only ever created in the hope that MacOS would be ported *for* Apple to other hardware, at the very best. At the worst, it may have been a simple ploy to try to attract developers from the OpenSource community. Basically, Apple suck almost as bad as MS. Just because they're a smaller dog than MS doesn't make them "the underdog" as we know it.

    5. Re:Mac OS X will unify the *BSDs by nrc · · Score: 1


      Holy Khrushchev Macman, were you banging your shoe on a podium during that speech?

      Really now, anyone who thinks the G4 has kept pace in the CPU wars can hardly be expected to understand why an open source OS doesn't correct the problems with running a proprietary GUI on proprietary hardware.

    6. Re:Mac OS X will unify the *BSDs by Anonymous Coward · · Score: 0

      *cough* darwin is available for x86 *cough*
      *cough* there is gnu/darwin os*cough*
      *cough* there is a package system based on apt called fink *cough*

      OS X's gui frontend and packaged software(i-tunes etc.) is the only thing about os X that is not "free".
      The base os is completely open and you are all free to start porting it to any arch that you like. Fly at 'er guys! Just because apple started darwin doesnt mean they own it! Use it, change it, improve it. It has the pottential to be as good or better than bsd, gnu/linux etc.

      and yes even though the gui costs $$$ it IS beautiful, sleek, fast, and easy to use.

      *note* I currently use freebsd, but played with darwin on my pentium 3 system with gnome 1.2 with sawfish, and it was a darling. Never gave me any problems.

      my conclusion for what it's worth: Even though os X is proprietary, the base system and it's ideals are great. Darwin is free as gnu/linux, and any bsd. don't be scared of software that had been touched by the big-boys(apple, m$)

      one last thought....os X with it's darwin underpinnings is a helluvalot free'er than solaris or irix.(think ppc vs other archs)

      When you open a tcsh term in osX it says "welcome to darwin" not "welcome to mac os"!!!

    7. Re:Mac OS X will unify the *BSDs by Anonymous Coward · · Score: 0

      *cough*APSL*cough*
      *cough*Apple Mac hardware*cough*

      Just because apple started darwin doesnt mean they own it! Use it, change it, improve it. It has the pottential to be as good or better than bsd, gnu/linux etc.

      Read the APSL, this time a bit more carefully...

      Note that Apple not only retains ultimate control of any APSL'd project, but also has control over *how* an APSL'd project is used...

      Let me reiterate a few points: the APSL is *less* free than the BSD license, and the fact that Apple still retains ultimate control over any APSL'd project along with the fact that Apple is one of the most *litigious* companies and an avid advocate of intellectual property "rights" is disturbing.

      Open/Free/NetBSD obviously doesn't suffer from any of those defects. As a NetBSD user and developer, I will *never* waste my time developing for Darwin/OS X.

      As much as I hate to say it, I must agree with Richard Stallman on this point.

      one last thought....os X with it's darwin underpinnings is a helluvalot free'er than solaris or irix.(think ppc vs other archs)

      Sure, OS X has APSL'd Darwin underpinnings, but it still has a proprietary GUI, which is the main thing that differentiates it from other Unices. And while certainly it is free'er than Solaris or IRIX, remember that NetBSD runs just fine on computers that normally run Solaris or IRIX (Sun Sparc and SGI MIPS), as well as a whole bunch of others as well, including Alpha, Sparc, m68k, VAX, PPC, etc.

      Darwin currently runs on two deficient platforms: ix86 and PowerMac. Big deal.

      I hate to say it but I think Apple's pulling a fast one on the mindshare of the BSD community.

      Let them use our source as a base for Darwin but let's not actively help them work on it; that to me is more of a waste than putting time into a GPL'd project.

    8. Re:Mac OS X will unify the *BSDs by Anonymous Coward · · Score: 0

      I agree with most of the things you said. I use FreeBSD now, but my point was that people who havent tinkered with darwin shouldnt just dismiss it. =)

  32. Re:Mirror of wonderful post by Anonymous Coward · · Score: 0

    Why do the Open Source people always have a lame excuse when their shit breaks/doesn't work?

    Boss: "MySQL/Apache/Linux/(Your favorite OSS project here) just choked and threw up on itself."

    Geeky OSS Admin: "Oh well that's because [yadda yadda yadda]. It's your fault. Jesus Christ, RTFM!!"

    It's the snooty attitude and god damned elitism of OSS geeks that the IT/computing world can do without. For one thing I'd bet $100 that IIS + MsSQL (shit even Oracle) wouldn't have choked there. Clearly there was enough bandwidth, so don't blame it on that this time. Let's take a nice deep breath and say it together: MySQL fucking sucks. That's better. Anyone ever remember winamp.com always fucking being down cause of MySQL? Yeah. When will you OSS-heads realize that your free shit will never compare or scale to pay-software. Anyone who would even remotely consider using MySQL for any remotely high level traffic site is a fucking idiot. (Don't give me that "Slashdot runs MySQL" bullshit; they run a load balancing server farm the size of my garage...) Oh yeah, now I remember the phrase. "You get what you pay for."

    For editing text files use Linux. For everything else there's Windows NT.

  33. yeah but,,, by fiftyfly · · Score: 2, Funny

    how would you pronounce that? "nut-bastard?"

    --
    "Sanity is not statistical", George Orwell, "1984"
    1. Re:yeah but,,, by questionlp · · Score: 1

      Or "not-BSD" or "not-Beastie" :)

  34. There is a huge need for something like this by mrbnsn · · Score: 2, Interesting
    Right now if you need any sort of third-party application support (Oracle, etc.) or kernel threads (Java Hotspot, etc.) you need to run a Linux kernel.

    If you don't need third party application support or kernel threads, however, FreeBSD has a much more solid, reliable kernel.

    It would be excellent if you could maintain different machines with different kernels as needed, but have everything on top of that be Debian (both because Debian is excellent, and because supporting a heterogenous OS environment is a pain best avoided if possible).

    1. Re:There is a huge need for something like this by neroz · · Score: 0

      You can, of course, run those third-party Linux applications in linux-emulation. Linux binaries typically run as fast on FreeBSD as they would on Linux. (I can't tell the difference between a Linux binary and a FreeBSD one).

    2. Re:There is a huge need for something like this by mrbnsn · · Score: 1
      I know this may be hard for some people to understand, but generally speaking, when you pay for a piece of commercial software, there is an expectation of commercial support for that software.

      Yes, it is possible to buy a Linux license for Oracle and run it (with some fiddling) on FreeBSD, but Oracle won't support it, which sort of defeats the purpose.

  35. Debian is an OS? by CheeseMunkie · · Score: 1, Offtopic

    *blink*

    I thought Debian was a distribution? That is, it's a kernel and assorted utilities. If we want to get right down to it, I always thought the kernel itself was the OS...

    What makes a distribution is its installer and software management. That is, the main difference between SuSE and Debian and Red Hat is yast, apt, and rpm. So... They're porting apt to NetBSD? That's well and good, but is both unnecessary and not worth this fanfare.

    1. Re:Debian is an OS? by Carlos+Laviola · · Score: 2

      Debian is independent of kernels. We have Debian Hurd already to prove that, and hopefully, we'll have Debian NetBSD, which will kick ass :-)

    2. Re:Debian is an OS? by someonehasmyname · · Score: 1

      no, the kernel is the kernel, and the os are all the apps debian wrote to interact with the kernel and the kernel. a windows nt machine uses microsoft's nt kernel, but it's still the windows os. all linux distros are their own os's with their own unique directory structure (debian puts rc files in "/etc/rc.d/rc1.d" whereas redhat thinks they should be in "/etc/rc1.d", etc.) netbsd, or more preferable freebsd (I had to plug it), supply their own kernel and userland apps that make up the os.

      --
      Common sense is not so common.
    3. Re:Debian is an OS? by Anonymous Coward · · Score: 0

      I don't think so; an OS is those utilities PLUS the kernel.

    4. Re:Debian is an OS? by Anonymous Coward · · Score: 0

      It isn't even a distribution. Red Hat is.

    5. Re:Debian is an OS? by Fluffy+the+Cat · · Score: 2

      They're porting apt to NetBSD?

      No, we're porting Debian to NetBSD. A distribution isn't just its installer and package management. There's the way the filesystem is laid out, the way the tools are configured by default and the philosophy behind the development.

    6. Re:Debian is an OS? by rking · · Score: 1

      I don't think so; an OS is those utilities PLUS the kernel.

      That's what he said, though the first sentence was rather clumsy :
      "no, the kernel is the kernel, and the os are all the apps debian wrote to interact with the kernel and the kernel."
      those last 3 words are to include the kernel as part of the os.

    7. Re:Debian is an OS? by Arandir · · Score: 1

      In the Debian world, the OS is anything that would cause RMS to explode if it didn't have the prefix "GNU".

      Orwell was right. GNU has been redefining the English language for 18 years, so it's to be expected that Gnuliban can't think straight anymore.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  36. They're not cooperating... by greygent · · Score: 1

    In fact, the BSD world seems largely annoyed at these folks.

    I personally don't see the reasons for this project, other than political. However, this is the beauty of the freedom of the BSD license.

    1. Re:They're not cooperating... by Carlos+Laviola · · Score: 4, Insightful

      Their motivation is quite clear to me: have another choice of a kernel that is already robust and better than the Linux kernel in certain areas, and have the nice, organized and easily upgradable Debian on top of it. Come on, building *everything* from source is so much more trouble than apt-get dist-upgrade. Think XFree86, Mozilla, etc.

    2. Re:They're not cooperating... by Fluffy+the+Cat · · Score: 2

      In fact, the BSD world seems largely annoyed at these folks.

      Really? We've got some BSD developers happily working with us. Nobody has yet actually made their displeasure at the situation known, other than some bitching on Slashdot-alikes. If they are annoyed, they're not annoyed enough to actually do anything about it.

      I personally don't see the reasons for this project, other than political

      That's why I went to the bother of writing this page.

  37. Re:Mirror of wonderful post by Anonymous Coward · · Score: 0
    I shall share your praise of this "MySQL" to my Fortune 500 boss by telling him that it was highly recommended by some guy named "AnimeFreak."

    Hot tip: Neither the words Anime nor Freak look good on a resume.

  38. I shoulda seen this one coming... by xcomputer_man · · Score: 3, Funny

    Finally, it's the GNU/BSD distribution!

    1. Re:I shoulda seen this one coming... by CatherineCornelius · · Score: 5, Funny
      Finally, it's the GNU/BSD distribution!

      Gnu's not Unix...except when it is.

    2. Re:I shoulda seen this one coming... by Anonymous Coward · · Score: 0

      Any BSD you can legally distribute freely is not UNIX (tm).

    3. Re:I shoulda seen this one coming... by styrotech · · Score: 1

      Any BSD you can legally distribute freely is not UNIX (tm).


      Thank you for that insight Rev Don Kool.

    4. Re:I shoulda seen this one coming... by Anonymous Coward · · Score: 0

      It's kind of funny, since NetBSD and Debian are both pretty much dead. Reminds me of those stories of dying cancer patients who meet during chemotherapy, and later chose to marry as they lie on their hospice deathbeds.

  39. Re:the kernel? my god man by CheeseMunkie · · Score: 3, Insightful

    " Theres a core group in charge of what goes and what stays."
    Actually, in Linux it's the same (f.e. Torvalds, Cox, Tosatti).


    This is true of the kernel, but the kernel is not the whole deal. One of the major problems with Linux is *that* it's every yahoo for himself -- Cox and Torvalds and a few others do the kernel, the glibc people are a different bunch, the X consortium, the ISC, Apache Foundation, plus all those assorted little libraries, you know the type, it's a kinda neat library, but you've only found 1 app that needs it ... Everyone does their own thing and contributes it to the slushpot, but nobody controls the pot.


    So, where the BSD team is some 10-20 people who can all get in a room and hash out details and come out with a coherent ports system, or a standard place to put software (apache goes in /var/www? Wtf patrick?), the Linux world is far too big to do that. Hell, we can't even document stuf coherently -- everything has its own man page, readme, manual, plus linux documentation project. Compare to FreeBSD's Handbook.


    This is a weakness in the Linux system of cooperation. It's also a strength. Just as no one can take control of the whole thing and fix it, also nobody can break the whole thing. Even if Linux and Cox between them decided to sabotage Linux, they couldn't, whereas one guy with cvs commit privileges on cvsup.freebsd.org could give himself a root shell on every BSD box on the planet. (Okay I exaggerate -- he'd get caught, probably, but that's only because most of the people working on BSD are good guys.)

  40. Re:That is so exciting *yawn* by Anonymous Coward · · Score: 0

    ATTENTION: this user is attempting lame humor. Do NOT moderate this as funny, as it is lame.

    Thank you,

    The Slashdot Anti-Sitcom-Jokes Brigade

  41. I don't like it by znu · · Score: 5, Insightful

    The thing I've always really liked about the BSDs is that they're complete and separate systems that include everything from the kernel to the userland tools, all integrated by one team. Compare with the Linux world, where you have a bunch of different distros that many people pretend are all the same OS (in spite of the fact that file systems are arranged differently, boot sequences are different, configuration is different, package management is different, userland tools are often different, etc.) because they happen to use the same kernel. The BSD way has always seemed a lot cleaner to me. The idea of seeing a myriad of distros based on the BSD kernels really isn't one that I like. I believe it's a step in exactly the wrong direction. Open source Unix needs more standardization, not more fragmentation.

    --
    This space unintentionally left unblank.
    1. Re:I don't like it by Skuld-Chan · · Score: 1

      Ever take a look in the linux kernel source? There's a lot of code and drivers that came from bsd...

    2. Re:I don't like it by Raving · · Score: 2, Interesting

      This is oh such a troll !

      Giving choice has never been a problem in the Open source world, and the good ol' argument about "all those people are wasting their energy, they should team up !" doesn't take into account the way people work.

      If anyone likes a project, he will join it. But if he doesn't, he will start hims. Is this a problem ? There is no such think as a best solution for the environment/distro/kernel choice ; being able to take whatever best fits your need is hence a big plus.

      --
      Singularity stupid: stupid gotten so dense that no intellect can escape
    3. Re:I don't like it by Ami+Ganguli · · Score: 2

      In a way this is standardization, just of a different kind. In the past, if I wanted to use both Linux and NetBSD I was forced to use too completely different operating systems. Different packaging systems, different user environments, etc. Now I can use the Linux, NetBSD, and Hurd kernels while sticking with my 'standard' Debian operating system.

      I, for one, welcome the idea. It makes it far more likely that I'll consider using the NetBSD kernel at some point in the future.

      --
      It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
    4. Re:I don't like it by Arandir · · Score: 2

      Except Debian isn't an operating system. The operating system will still be NetBSD. The Debian bits could be called the operating environment, but it certainly is not the software that directs and controls processes, manages access to hardware, etc.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    5. Re:I don't like it by IkeTo · · Score: 1

      > Compare with the Linux world, where you have a
      > bunch of different distros that many people
      > pretend are all the same OS (in spite of the fact
      > that file systems are arranged differently, boot
      > sequences are different, configuration is
      > different, package management is different,
      > userland tools are often different, etc.) because
      > they happen to use the same kernel.

      That makes it extremely easy... just use <add-your-dist-name-here>Linux! I use Debian GNU/Linux, and every installation of Debian GNU/Linux use the same boot seqence, same filesystem hierarchy, same configuration, same package management, same set of userland tools which can be chosen by sys-admins, ... There is no diversity to deal with!

      Well... there is version differences, but there is version differences even in BSD, so it shouldn't count. ;p

      How about the size of user base? Well... Just Debian GNU/Linux beats all BSD summed together hands-down! So don't worry about specializing just in Debian, it is still better than BSD!

      If you don't think that "Linux" suffices to pinpoint your knowledge about your OS, just be more specific.

    6. Re:I don't like it by Ami+Ganguli · · Score: 2

      That's entirely a matter of definition. I think saying that the operating system consists of only the kernel (which is arguably the least visible component) is a bit of a stretch. The Microsoft position that the operating system is everything that's shipped on the CD is a little extreme as well.

      --
      It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
    7. Re:I don't like it by Arandir · · Score: 1

      That's entirely a matter of definition.

      Everyone has their own definition, which is why I use the definition in the dictionary (www.m-w.com). Turns out that despite RMS's protests to the contrary, emacs, gnuchess and GNOME are not parts of an operating system.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    8. Re:I don't like it by Ami+Ganguli · · Score: 2
      ...controlling input and output functions.

      GNOME controls input and output functions (along with X). That would make it part of the operating system according to the M-W definition.

      --
      It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
  42. Re:Mirror of wonderful post by Anonymous Coward · · Score: 0

    Wow, this troll is so inovative that I fell for it completely! You truly are a troll genius!

  43. Incestuous or not? by alex_delarge · · Score: 0, Troll

    Feels right, but is it really wrong?

  44. Don't have to install from source... by greygent · · Score: 2, Informative

    In the BSD world, we not only have the ports collection, we have the packages collection, too. So there's no need to compile everything from ports :-)

    1. Re:Don't have to install from source... by Carlos+Laviola · · Score: 2

      But do you keep this as updated as the ports collection? Because Debian is the equivalent of running a bleeding-edge *BSD, I think (updated by CVS daily, rebuilding the whole system as often as possible).

    2. Re:Don't have to install from source... by Carlos+Laviola · · Score: 2

      And of course, the user doesn't need to build from source, only fetch the latest packages available. If he uses the unstable branch of Debian, he's getting all the latest goodies, often ASAP.

    3. Re:Don't have to install from source... by neroz · · Score: 0

      Unfortunately this only applies to -RELEASE, since binary packages are not made available for -STABLE (theses are equivalent to debian stable and debian testing). If you run anything but -RELEASE, you have to compile from ports. You can, of course, make sysinstall think you run -RELEASE, and install the old binaries from -RELEASE, but there is always the chance that they are no longer compatible with your current(-STABLE) system.

    4. Re:Don't have to install from source... by T-Punkt · · Score: 2, Informative

      Since you mention -STABLE you're obviously talking about FreeBSD.

      For NetBSD (and I'm pretty sure for OpenBSD as well) there's no need to make seperate sets of precompiled packages for -current and RELEASE since packages made for RELEASE run on -current as well.

      (There's no NetBSD -STABLE tree, just -current and RELEASE.)

    5. Re:Don't have to install from source... by neroz · · Score: 0

      Woops, yes I was talking about FreeBSD. Do you know how the SMP effort in netbsd is going? (They have an effort for SMP don't they?)

  45. I support it as a server over debian linux by Billly+Gates · · Score: 2, Troll
    Linux has some serious issues . I like the Freebsd development model better then linux thanks to all the issues with the 2.4 patches. My problem with FreeBSD is that its cripppled after the install is done. Hardly anything is configured. I feel like a kid stuck on a pogo stick when trying to do anything. For example under WindowMaker you need to put every item one by one to the x menu. No config menu's here. Also not even bash or frankly any shells besides the crippled bsh is installed by default. You need to edit all the files yourself assuming your unix literate. All just to learn it. That is crazy. Why? What a pain. Its not FreeBSD per say but unix in general that suffers from this. Linux breaks the mold. Unless you have 5 years expereince or a cs degree you can not really tune it or highly configure it. In Windows you can just point and click and all the items are in the start menu by default. There is an old saying. IF computers were airplaines the unix one would be the best. However you would need to assembly it yourself. I believe Linux took off because the distro's configure everything for you. Don't get me wrong when I say that BSD is a great server OS. I just hope debian *bsd will fix this which actually knowcked unix almost out of the workstation market. I have never used debian linux so I don't know how much is configured by default during installation. I just assume its better then the current netbsd.

    1. Re:I support it as a server over debian linux by Anonymous Coward · · Score: 0
      Unless you have 5 years expereince or a cs degree you can not really tune it or highly configure it.

      heh you should meet those certain people with CS degrees who can barely handle windows. but seriously, what does it matter if windowmaker is easy to setup. freebsd isn't meant to be a desktop OS. people who would use it for that probably know how to tweak that stuff anyway.
    2. Re:I support it as a server over debian linux by Anonymous Coward · · Score: 0

      Why would you want unix to have everything set up for you? One of the main points of the Unix style operating systems is the fact that you can customise it to your needs. No one can say what your needs will be so setting every thing up does more hurt then good. Take most Linux distros for example, they install nice and set everything up, but who needs every service known to man, that is insecure and especially bad for server enviroments. A good admin is going to customise and set everything up the way they want it anyway and its much better to start from a clean system then have to undo everything. It is also a complete overstatement to say that it will take 5 years to learn how or a cs degree. For one cs barely skims the outer surface of unix, only experiece matters. Secondly, while the system is complex, it can be fully grasped in a couple of months, really all you need to know is basic networking, what programs you need, and the ability to use a text editor. Oh and the most important things are patience and the ability to read.

    3. Re:I support it as a server over debian linux by archen · · Score: 1

      I'm not sure this guy should be moderated down as a troll since I find what he says to be somewhat true. I used Linux for a while before I switched to FreeBSD (which I'm much more happy with). The first thing to keep in mind is that of course BSD expects you to do your howework. No cute configureation utilities with BSD. But with that said, (as the post above states) there are gaping holes with certain parts of the install. My main gripe was also with Window Maker and bash. I mean if I choose bash for a shell, I would hope that the correct rc/profiles are copied (or even created) but they are not. Window Maker I found to be especially annoying. If I use Window Maker I would EXPECT that the X apps that I installed would be on the menu. Again this isn't the case. You instead end up with a generic config - much of which was a bunch of things on the menu for things I didn't even install (thus pointed off into lala land).

      Now some people say FreeBSD isn't a desktop OS. To me FreeBSD is as much a desktop OS as Linux is for the most part. KDE is KDE as far as I'm concerned, reguardless of OS. But there are some people (such as myself) that like to use X on more serious machines in order to see more than one terminal window at once, for which a lower footprint WM like Window Maker or fvwm are perfect.

      It's just a bit of nit-picking about BSD. If they are going to offer the option, then they need to pull their head out of their arse and CONFIGURE that option (not the half assed here you go, figure it out yourself).

    4. Re:I support it as a server over debian linux by Arandir · · Score: 2

      For example under WindowMaker you need to put every item one by one to the x menu.

      That's the way it is supposed to be. Windowmaker is not FreeBSD and FreeBSD is not Windowmaker. They are separate projects. For FreeBSD to come along and decide what entries you must have in your wm menu would be the height of arrogance.

      I used a Linux distro once that kept modifying my Windowmaker menu. It drove me nuts. I kept removing stuff and Redbutt kept putting it back in. So I tried another distro and it did the same damn thing, but went several steps further by removing every manual configuration I made every time it booted.

      Dammit! Leave my configuration alone! If some distro wants to ship with default configs for the newbies, more power to them. But don't touch my configs after I do. That's more than rude, it's Evil.

      Unless you have 5 years expereince or a cs degree you can not really tune it or highly configure it. In Windows you can just point and click and all the items are in the start menu by default.

      Since when did you need a 5 year degree to add items to a menu?

      I believe Linux took off because the distro's configure everything for you.

      Linux took off long before the hand-holding distros should up. Go use Redhat 4.2 and see how easy it is. It was a nightmare of unusability. But it was the most popular distro at the time the world begin to discover that there was such a thing as Linux.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  46. Interesting Linux Mentality by pHDNgell · · Score: 1

    For the longest time, people would argue about how Linux isn't an operating system, just a kernel from which an operating system is made. Now people are going out there and taking a complete operating system, pulling a part out of it, and sticking it in the middle of what was normally a Linux distribution.

    Linux is a Kernel without an operating system. NetBSD is a complete operating system where everything is designed to work together seamlessly.

    What's next, DebiaNT?

    --
    -- The world is watching America, and America is watching TV.
  47. how different (from standard netbsd) is it? by foonf · · Score: 3, Insightful

    Did they just port apt and dpkg, and put up some Debian-packaged NetBSD binaries? Or have they moved to a Sys V init system, ported the Debian administration and configuration tools, and all the other stuff that makes debian distinctive? They explicitly say that NetBSD doesn't support runlevels, and looking at the package list, it doesn't look like much of the debian tools have made it yet.

    If its just a different package system, its pointless. Less work, and more immediately useful results, would be modifying apt to work with the current binary package system (which actually does support dependencies, etc.), and the large number of binaries in this format already available.

    If not, its a more questionable proposition. Arguably, its not really BSD anymore...it runs NetBSD binaries and uses that kernel, but the userland is basically Debian, ie, just like any Linux distribution. And most people who want that should just assume use Debian with the Linux kernel, which is a far more mature combination. Yes, for VAXen, toasters, slide rules and other more arcane platforms this won't exactly work, but Debian-NetBSD doesn't seem to have package for these platforms anyway.

    --

    "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    1. Re:how different (from standard netbsd) is it? by pHDNgell · · Score: 2, Informative
      Or have they moved to a Sys V init system

      This would be a pretty big step backwards. The NetBSD startup stuff is far superior to SysV. They wanted to move to a similar model for a while, but anyone who's ever used SysV startup on a real system understands the problems.

      Their current system allows you to drop files in a directory for startup that contain no special file names. They may list internally what service they provide, and what service they require and they will be sequenced properly. If you run two things that require network and don't provide anything that anything else requires, they'll get run after the network portion of the startup runs. There is no special shell scripting based on requested command (i.e. how many SysV startup scripts have you seen that implement ``start'' but not ``stop?''). Best thing is they're tiny, and they grow with the system. You define a couple variables and then do ``run_rc_command "$1"''

      I think it's cool that people are trying different things, and I don't care as long as it's not wasting me money, but they'd probably be better off learning from a system rather than trying to assimilate the kernel while throwing away the other good stuff.

      --
      -- The world is watching America, and America is watching TV.
    2. Re:how different (from standard netbsd) is it? by neroz · · Score: 0

      The project is very immature, even though the mailing list dates back to 1999, the project was picked up and dropped by many different people many times (have a read of the list if you like). This is a new start, and looks to be the most promising so far. As for the init system, sticking with NetBSD's init would be a good idea, but the debian zealots will most likely want a wrapper for it, so that the package init update scripts can work without having to consider two different init systems. It's not all that difficult, and we still get to keep NetBSD's init :-) The end goal is to get a full debian system on top of a BSD kernel, some of the userland tools may stay BSD, some might be changed to GNU. It depends on who wants what, and if any scripts choke on the different syntaxes of the same tools (eg. BSD ifconfig and GNU ifconfig have different output).

    3. Re:how different (from standard netbsd) is it? by Fluffy+the+Cat · · Score: 3, Informative

      Apt and dpkg have been ported. We're working on porting the administrative and configuration utilities. The idea is not to just package NetBSD binaries - the idea is to build the Debian source packages on NetBSD except in cases where that's impossible, and in those cases to produce packages that provide as much of the same functionality as possible.

      Less work, and more immediately useful results, would be modifying apt to work with the current binary package system

      I'd argue with the "less work", but anyway. Connectiva have ported apt to work with RPMs - that doesn't make it Debian. We're not trying to produce a NetBSD varient using Debian packaging tools. We're trying to produce Debian running on top of the NetBSD kernel.

      Arguably, its not really BSD anymore

      By some values, this is probably true.

      Debian-NetBSD doesn't seem to have package for these platforms anyway

      Yet. Once we're running on one architecture, this ought to happen.

  48. Do you care about your kernel? by BrookHarty · · Score: 2, Interesting

    I started using linux because it had the hardware support I needed, and support was 100x better. But it wasnt stable enough for my server, so I ran freebsd. But that was a few years ago. Ive always been able to explain to my friends who run BSD, that I need SMP support, so I run linux. But its also how linux has better configuration utilties and drivers. After using linux for years, I know where everything is, easy to setup and fix.

    Now, Linux is rock solid, and I get to laugh at my friends who cant X setup on thier freebsd boxes. But then, by the time a good bsd distro will be out, newer and better linux kernels will be out, with new vm's and more features.

    -
    The most exciting phrase to hear in science, the one that heralds new discoveries, is not 'Eureka!' (I found it!) but 'That's funny ...' - Isaac Asimov (1920 - 1992)

    1. Re:Do you care about your kernel? by Anonymous Coward · · Score: 0

      Your statements are almost as ignorant as your use of the english language. Setting up X on FreeBSD is a painless experience. Have you heard of /stand/sysinstall?

    2. Re:Do you care about your kernel? by BrookHarty · · Score: 2

      That is not a troll post.
      Does netbsd support SMP yet? Valid points.

    3. Re:Do you care about your kernel? by kan · · Score: 1

      They posted screenlog of the multiprocessor VAX box booting NetBSD some time ago. This is probably the oldest working SMP machine in existence.

    4. Re:Do you care about your kernel? by Arandir · · Score: 1

      I get to laugh at my friends who cant X setup on thier freebsd boxes.

      Funny, it's the same damn X on *BSD and Linux. It installs and sets up exactly the same. Now if you're talking about Linux front ends that try to simplify the procedure, like DrakX which has never failed to royally hose my XF86Config, you can have them.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    5. Re:Do you care about your kernel? by The+Finn · · Score: 1

      there is support in -current for SMP on i386, VAX, and alpha. (links are to old posts in tech-kern.) work is in progress for sparc, mips, and maybe a few others. (m68k?)

      one of the goals is to get SMP branches merged back into the trunk for 1.6.

      --
      NetBSD: the cathedral vs the bizzare.
  49. Transition by tiny69 · · Score: 4, Insightful

    Not too long ago, someone made the comment on slashdot about the general progression of Linux users. As a users becomes more experienced with Linux, they tend to shift from:

    Mandrake/RedHat -> Debian/Slackware -> *BSD

    It seems that Debian is going to make that last transition a little easier.

    --
    Go not unto/. for advice, for you will be told both yea and nay (but have nothing to do with the question)
    1. Re:Transition by Anonymous Coward · · Score: 0

      Since when apt-get is for experienced users ?

    2. Re:Transition by Anonymous Coward · · Score: 0

      well said, and so true!

    3. Re:Transition by yobbo · · Score: 1

      It all depends on how many stories are posted about specific distro's. If the number of stories about mandrake or SuSE were higher than other distro's, then naturally you'd have a higher total of debian loving posts. It is the same with Gnome or Kde. If there were alot more stories about gnome, then one's general perception of the "progression of linux users" would be that KDE is the most stable and user friendly desktop for linux, and that they are all refugees from Gnome.

    4. Re:Transition by Anonymous Coward · · Score: 0

      apt-get is great for experienced users - you can spend your time working with the computer and using it as a tool rather than fighting with dependancies and installing apps. You know that keeping your system up to date is a real no brainer even if you're the other side of the world ssh'ing in from a palm through a mobile phone.

      My debian boxes stay running, stay up to date and stay secure. I spend my time doing my job and not worrying about them.

    5. Re:Transition by Anonymous Coward · · Score: 0

      apt-get is great for experienced users - you can spend your time working with the computer and using it as a tool rather than fighting with dependancies and installing apps. You know that keeping your system up to date is a real no brainer even if you're the other side of the world ssh'ing in from a palm through a mobile phone.

      My debian boxes stay running, stay up to date and stay secure. I spend my time doing my job and not worrying about them.

    6. Re:Transition by Anonymous Coward · · Score: 0

      > Mandrake/RedHat -> Debian/Slackware

      Funny, I went the exact opposite way! I don't have time to maintain or mess around with setting up my *nix firewall box.

    7. Re:Transition by Anonymous Coward · · Score: 0

      Mandrake/RedHat/SuSE -> Debian/Slackware -> LFS

    8. Re:Transition by m_ilya · · Score: 4, Interesting
      Funny but I've switched my desktop OS in slightly different order:

      RedHat -> Slackware -> FreeBSD -> Debian

      For desktop OS I find Debian Linux more convient than FreeBSD for two reasons:

      • Linux have better support for multimedia devices than FreeBSD
      • Debian have more prepackaged software than FreeBSD and in general quality of debian packages is better than FreeBSD ports thanks for Debian strict packaging policy.

      --

      --
      Ilya Martynov (http://martynov.org/)

    9. Re:Transition by Anonymous Coward · · Score: 0

      I find that while this isn't really true in general, it tends to be the case with '1337ness'. As linux moves toward the mainstream, there is less incentive for the people who just want to be 'better' then others. You even see this within the BSD world, with people moving towards netBSD, which has absolutly no redeeming qualities over freeBSD, unless you are running some obscure piece of hardware.

      I saw let them go, dump all the 'style' over substance people who run all possible services and never learn to code well on the netBSD people. The rest of us can choose something that we like and stick with it. For me thats debian, but Redhat/Mardrake and FreeBSD are all perfectly good.

    10. Re:Transition by mdw2 · · Score: 1

      I made that exact same transition, as my first installation was redhat, after a couple months, i just couldn't stand RH any more, then i moved to slack. Eventually when i had some hardware failures i decided to go with freebsd, that lasted about 8 hours, because i realized i couldn't get hardware accelerated openGL for my geforce2mx in freebsd. I'm not sure if this is still the case, hopefully it's not, as I would love to be able to use freebsd more, simply because i LOVE /usr/ports.

      --
      This sig intentionally left blank.
    11. Re:Transition by Arandir · · Score: 1

      Linux have better support for multimedia devices than FreeBSD

      A valid reason. But don't go to overboard in demanding multimedia support, or you'll end up using Windows :-)

      Debian have more prepackaged software than FreeBSD

      FreeBSD has 99% of what Debian has. Of that remaining 1%, they're 99% Linux-only programs. Who needs linuxconf on *BSD anyway?

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    12. Re:Transition by m_ilya · · Score: 1
      FreeBSD has 99% of what Debian has. Of that remaining 1%, they're 99% Linux-only programs. Who needs linuxconf on *BSD anyway?

      I had FreeBSD on my desktop for three months (and I still use it on servers) and I'm using Debian Linux testing now for long time so I've some experience with both systems. Belive me there are tons of software which I use and which are not in FreeBSD's port collection but are avialable as Debian packages. It is not 1% and is not Linux specific.

      And anyway I belive quality of packages in Debian is higher. At least I have seen much more problems with FreeBSD ports than with Debian packages.

      --

      --
      Ilya Martynov (http://martynov.org/)

    13. Re:Transition by Arandir · · Score: 2

      "There are currently 6376 ports in the FreeBSD Ports Collection." [http://www.freebsd.org/ports/index.html]

      That's a hell of a lot of software. It's a hell of a lot more than Debian -stable (3950). But I here you cry that Debian -unstable is really stable so I should consider that instead, even though Debian still calls it -unstable. Trouble is, there's no official count of the number of packages in -unstable (and I'm not about to count them by hand).

      So I did an unofficial, by the seat of my pants, survey of Debian packages. It turns out that Debian has a very high atomicity for it's packages. In other words, what is one package on FreeBSD might be two or more packages on Debian. Examples include splitting a library up into base, development and examples packages, a greater preponderance of "meta" packages (like koffice being split up into nine packages, plus the "development" package), and duplicate packages differing only in their build options (dia, fluxbox). Other oddities include dozens of kernel versions and dozens more kernel patches, splitting the KDE wallpaper out into it's own package (huh?).

      Going by package count is definitely NOT the way to compare FreeBSD and Debian.

      So far I haven't found any software that I wanted that was in Debian but wasn't in FreeBSD. But what if I did? Well then, I would simply turn on FreeBSD's Linux compatibility Mode!

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    14. Re:Transition by m_ilya · · Score: 1
      Going by package count is definitely NOT the way to compare FreeBSD and Debian.

      Well, just some facts. Some software I use:

      • eudc (LDAP interface in emacs) - is in Debian but not in FreeBSD until I submited port
      • gnuserv (port of xemac's gnuserv) - is in Debian but not in FreeBSD until I submited port
      • gnus (recent version popular newsreader for emacs) - is in Debian but not in FreeBSD until I submited port
      • perl modules (I do a lot of Perl) - Debian have more than FreeBSD
      As for FreeBSD's Linux compatibility mode: it is cool but you should understand than every big Linux application will require to install Linux versions of all libs. Also you are out of lack if you want to use Linux packages and have package managers to track their dependacies. At this point it becomes much more easier just compile from source.

      Actually I think the only reason to use FreeBSD's Linux compatibility mode is closed source software for Linux.

      --

      --
      Ilya Martynov (http://martynov.org/)

    15. Re:Transition by Arandir · · Score: 1

      There will always be one OS/distro/system somewhere that happens to have to most software available. Currently that happens to be Windows. But somehow I don't think Debian users are going to suddenly switch to Windows. The number of packages available on a system is largely irrelevant to the user. All they want to ensure is that there's a sufficient number of packages that they're not spending a significant amount of their time hunting stuff down.

      Now let's suppose that two different distros each of 10,000 packages. Will they have exactly the same packages? Of course not. If you choose one of those distros you will eventually discover that they other has the software that you want.

      Instead of nitpicking Debian-vs-FreeBSD to death, let me rephrase my original assertion: "FreeBSD has 99% of what you want. Of that remaining 1%, it's not worth switching over."

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    16. Re:Transition by rawg · · Score: 1

      I went like:

      debian(95) -> slack(96) -> debian(96) -> redhat(97) -> debian(97) -> freebsd(01) -> debian(01).

      I really like the BSD system, but I dont like download, compiling and installing 100's of MBs of software. I'll stick with Debian, but I'll switch to DebianBSD when its working well. Long live APT.

      --
      The above is not worth reading.
  50. Re:Mirror of wonderful post by Metrollica · · Score: 0

    Geeky OSS Admin: "Oh well that's because [yadda yadda yadda]. It's your fault. Jesus Christ, RTFM!!"

    You know you're a geek when you use UNIX abbreviations in speech.

    RTFM /R-T-F-M/ imp.

    [Unix] Abbreviation for `Read The Fucking Manual'.
    1. Used by guru s to brush off questions they consider trivial or annoying. Compare Don't do that then! .
    2. Used when reporting a problem to indicate that you aren't just asking out of randomness . "No, I can't figure out how to interface Unix to my toaster, and yes, I have RTFM." Unlike sense 1, this use is considered polite. See also FM , RTFAQ , RTFB , RTFS , STFW , RTM , all of which mutated from RTFM, and compare UTSL .

    -Metrollica

    --



    --Metrollica
  51. What does FreeBSD have to do with anything? by pHDNgell · · Score: 2, Informative

    Your complaints about NetBSD are a result of your experience with FreeBSD? These are completely different *operating systems* (not kernels, full operating systems).

    Windowmaker is not BSD. If you have a problem with Windowmaker, go complain to them.

    Which parts of tuning require five years of experience and/or a CS degree? I switched from Linux to NetBSD after I'd been using computers for about two years altogether, and have always found it easier to work with. Why? Because it's a whole operating system. If stuff goes into the kernel, it's released with userland support, all at the same time.

    NetBSD is, IMO, the cleanest system out there today. Everything works, and moving forward is easy. Doesn't come with bash? So what? I don't use bash, so I'm pretty happy to not see it. I do like the standard bourne shell it comes with for running my scripts. I do use tcsh, so it's typically one of the first things I install from pkgsrc on a new machine.

    ``But pkgsrc is hard! You have to build the stuff yourself,'' you say? A ``make package'' at the top level will create binary packages for the current platform for all packages your configuration suggests you're licensed for. Port maintainers typically do this and provide binary packages for most things people would want. In fact, when NetBSD releases ISOs, they release pre-built package ISOs for i386, just to make it a bit quicker (it certainly can't be any easier).

    --
    -- The world is watching America, and America is watching TV.
  52. quiet you! by gnurd · · Score: 1, Troll

    no linux! please leave bsd alone. we were doing just fine thank you, go make another revolution somewhere else. we dont want microsoft targeting us next. we are much happier having them use our code instead.

    --
    "i was saying gnu-rd"
  53. GNU OS by Proud+Geek · · Score: 2

    As Richard Stallman has been saying all along, the OS is GNU, and the kernel it runs on, be it HURD, Linux, or now NetBSD, is just that: the kernel. Of course, Richard is now chorling at the thought of further showing the irrelevance of Linux, but if people call it the Debian Operating System (DOS???) instead of GNU, he'll quickly change his tune and go back to righteous indignation.

    --

    Even Slashdot wants to hide some things

    1. Re:GNU OS by cmkrnl · · Score: 1

      So tell me this now. Does that theory apply to a NT box running Cygwin for example ? Or a VMS System running gnu userland packages ?

      Or are you just A.N Other RMS groupie with zero insight. Queueing like all your GNU wannabes, not an original thought among you, waiting for the honour to fellate the guy, whose take on how the world should be, is hypocritically self indulgent.

      Free Software is only free if your time is worth nothing. Its a pity the GNU Socialist whose whole working life whas been funded either out of the public purse or the largesse of others deliberately fails to see that.

      Curmudgeon

  54. Debian's making a good choice by Anonymous Coward · · Score: 0

    Who can really blame them for starting to move toward *BSD and getting the Hell away from the AOL OS, er I mean, Linux?

  55. postgresql would help these guys out by Anonymous Coward · · Score: 0

    I have to take this moment and pimp the upcoming
    release of the postgresql RDBMS. Postgresql scales
    much better than mysql, and is infinitely more
    powerful from a data-management perspective. Oh
    yeah, they'd also be better off using a real
    language like (perl|python|ruby) instead of that
    bloated, non-designed, non-language macro expander called php.

    ... cause a good old fashioned troll can actually
    be true.

    b

  56. *BSD More Secure? by ryanisflyboy · · Score: 1

    I've heard a lot of talk at the local ISP (who gave up Linux for FreeBSD) that *BSD is some how more secure (which IMHO is relative). Why would an ISP think such a thing? And, if infact it is somehow more secure, then isn't having the wonderful tools of Debian running on it very very good? Regardless, I think it's really neat to see Debian growing in all kinds of interesting directions.

    1. Re:*BSD More Secure? by Anonymous Coward · · Score: 0

      Because all you need to know is how to setup cron and cvsup and you will always be up to date, thus secure.

    2. Re:*BSD More Secure? by 8bit · · Score: 2, Informative

      FreeBSD has kernel level security options. Once you set a security level you cannot set it at a more relaxed level without rebooting. With features like that in place, it becomes very hard for a cracker to gain complete control over your server. Reboots are pretty dawg-gone noticable, don't ya think?

      --

      --Roy
  57. Splintering by Alcemenes · · Score: 1

    At this rate there will be three independant open source platforms; Linux, *BSD and Debian. I see no real problem with this but I just don't understand the point. One other question; if Debian is the most pure Linux in an open source point of view why are they porting it to a more restrictive licensing scheme?

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

      Oiy! You loon. The BSD license is several orders of magnitude less restrictive than the GPL. Go read them both. Write 5,000 words on why you're wrong.

    2. Re:Splintering by cmkrnl · · Score: 1

      Here we ago, yet another RMS groupie. Go read the damn thing before spouting such nonsense in future.

      curmudgeon

    3. Re:Splintering by The+Ape+With+No+Name · · Score: 2
      One other question; if Debian is the most pure Linux in an open source point of view why are they porting it to a more restrictive licensing scheme?


      How is the BSD license more restrictive? It allows for free and non-free use. It is actually more open than the GPL and probably better for students as it allows them the freedom to carry their work away from school. Does the GPL do this?

      --
      Comparing it to Windows will be a moot point, since El Dorado is going to have a 40% larger code base than XP.
    4. Re:Splintering by Burnon · · Score: 1

      Odds are, the people doing this aren't concerned about licensing purity, and just like the technical features.

  58. actually the joke is as follows by Niksie3 · · Score: 0

    UNIX Airways

    Everyone brings one piece of the plane along when they come to the
    airport. They all go out on the runway and put the plane together piece
    by
    piece, arguing non-stop about what kind of plane they are supposed to
    be
    building.

    Air DOS

    Everybody pushes the airplane until it glides, then they jump on and
    let
    the plane coast until it hits the ground again. Then they push again,
    jump
    on again, and so on ...

    Mac Airlines

    All the stewards, captains, baggage handlers, and ticket agents look
    and
    act exactly the same. Every time you ask questions about details, you
    are
    gently but firmly told that you don't need to know, don't want to know,

    and everything will be done for you without your ever having to know,
    so
    just shut up.

    Windows Air

    The terminal is pretty and colorful, with friendly stewards, easy baggage check and boarding, and a smooth take-off. After about 10 minutes in the air, the plane explodes with no warning whatsoever.

    Windows NT Air

    Just like Windows Air, but costs more, uses much bigger planes, and takes out all the other aircraft within a 40-mile radius when it explodes.

    Linux Air

    Disgruntled employees of all the other OS airlines decide to start their own airline. They build the planes, ticket counters, and pave the runways
    themselves. They charge a small fee to cover the cost of printing the ticket, but you can also download and print the ticket yourself.
    When you board the plane, you are given a seat, four bolts, a wrench and a copy
    of the seat-HOWTO.html. Once settled, the fully adjustable seat is very comfortable, the plane leaves and arrives on time without a single problem, the in-flight meal is wonderful. You try to tell customers of the other airlines about the great trip, but all they can say is, "You had to
    do what with the seat?

    --
    Sig you!
  59. Re:Mac OS X will unify the *BSDs - MOD DOWN by Anonymous Coward · · Score: 0

    Oh my god...

    Will someone please make the apple fanboy stfu!

  60. ports by lightfoot+jim · · Score: 5, Insightful

    What exactly is the ports system?

    More like, what are rpm users missing out on? With rpm -i package.rpm the user may or may not be able to install the intended software. There could be real dependency problems, as in kde2 needs qt2. There could also be bogus dependency problems since you may have compiled qt2 from source but rpm wouldn't know about it.

    Enter FreeBSD and ports. A typical FreeBSD install creates a directory called /usr/ports which is a whole tree of makefiles. So to install something, you just cd /usr/ports/category/WhateverYouWantToInstall/ && make && make install. All dependencies are taken care of automagically. The makefiles in these directories are smart enough to download whatever you need and then compile the source on your machine. So installing a new package doesn't take several hours of trolling newsgroups and searching for rpms.

    But you don't have to take my word for it. Check this out.

    My experience is limited to Mandrake, Slackware, FreeBSD and OpenBSD. They each have their strengths and weaknesses, but when I need to get sh*t done, BSD, espescially FreeBSD is my first choice just because the ports tree contains nearly any software I'd want to run, eliminating the bottleneck that software installation sometimes turns into and letting me get to the task at hand.

    As an aside, it seems like everything that Mandrake tries to be to "joe sixpack" who is just getting into trying linux on the desktop, BSD is to the sysadmin or programmer who needs to get a *nix platform up and running for a certain task. Compiling a custom kernel, installing software, modifying the init process, etc are at least as easy for the sysadmin on BSD as adjusting the screen fonts and changing the wallpaper are for a newbie in Mandrake.

    --
    The state is the great fiction by which everyone tries to live at the expense of everybody else. ~F. Bastiat
    1. Re:ports by damiam · · Score: 1
      There could be real dependency problems

      Enter Debian and apt-get.A typical Debian install includes a program called apt-get that handles dependencies automatically. So to install something, you just apt-get install WhateverYouWantToInstall. All dependencies are taken care of automagically. The apt-get program is smart enough to download whatever you need and install it. To compile from source, use apt-get -b source WhateverYouWantToInstall. So installing a new package doesn't take several hours of trolling newsgroups and searching for rpm.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:ports by lightfoot+jim · · Score: 1

      Yep, apt-get is great, or so I've been told. The reason I didn't mention it in my initial post is that I don't have any experience with Debian which makes me unqualified to praise or criticise it. Since I live out in the middle of nowhere, my only internet connectivity option is a dialup account from a company that has more customers than bandwidth. When I downloaded Slackware, it took me 3 days. Because FreeBSD has impressed me more than linux in several areas besides than software management (kernel compilation, documentation, cleanness of a base install, only one "distro," etc.) I've not been in any real hurry to download and try out Debian. I probably will at some point, but it's just not a priority. I suppose it makes me a minority here, but I don't look at installing and configuring software as a means of recreation. I consider it a necessary chore in order to use my computer to read email, listen to music, surf the www and crunch numbers for certain statistical projects I'm working on. If I saw any indication that Debian could reduce that chore more effectively than FreeBSD, I'd set aside another three days. At the moment it looks like a toss-up at best, so I stick with what I have.

      --
      The state is the great fiction by which everyone tries to live at the expense of everybody else. ~F. Bastiat
    3. Re:ports by Anonymous Coward · · Score: 0

      You missed one more thing, as well.

      They have released a version of apt-get to work on redhat rpm's. Redhat users can now apt-get their way to nirvana. ;^) If you don't feel like apt-get you can always go for ximian's red-carpet, a graphical installer that makes it pretty easy to install/deinstall packages.

      Oh, and now that there are www.rpmfind.org mirrors rampant it's not that hard to download and install rpms. And since SRPMS exist, you can compile the rpm yourself, using your own exacting specifications. And if you want bleeding edge software, then you can make your own rpm which really isn't that hard to do.

      When you come down to it, people will or will not like a particular package management system just the same way they will or will not like a particular distribution that starts with an "R".

    4. Re:ports by SpinyNorman · · Score: 2

      How is this any more convenient than apt-get which is also available for RPM based systems?

      Personally I find that I rely on the installed RPMS of most everything (and once in a while upgrade my distro to get the newer X, KDE etc), and simply compile from tarballs anything that I really care about and want to be up-to-date with, which basically means development libraries and a few cutting edge utilities. It works for me.

    5. Re:ports by scrytch · · Score: 4, Insightful

      > How is this any more convenient than apt-get which is also available for RPM based systems?

      Because ports does not require packages. Example, if I want to install a KDE app, it does not require that I have the qt package installed. It searches for libqt.so. If it's a gtk package, it runs gtk-config, if it's apache, it runs apxs, and so forth. Now debian's a little better than RPM, which ends up making you force-install just about everything (defeating dependency checking) because you installed something from source, but you still have to intervene when a dependent package isn't present. Ports assumes you know what you're doing, and if the lib is there, it's there, it doesn't need a package manifest to tell you. It does check for the package first, and ports does build a package, so you get a package-based system that degrades gracefully when you don't religiously use the package system.

      THAT is why I use ports. Because no sysadmin I know of takes the builds out of the box, they keep their source trees around to tweak and recompile as needed. Oh, and ports lets me do that doo, I just "make get" the port, cd work/packagename, and there's the source tree as if I'd untarred it myself. I can configure && make install it from there, or cd ../..; make install from there and it builds as a package.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    6. Re:ports by Anonymous Coward · · Score: 1, Interesting

      If I saw any indication that Debian could reduce that chore more effectively than FreeBSD, I'd set aside another three days. At the moment it looks like a toss-up at best, so I stick with what I have.

      Well, I can guarantee you that Debian will solve virtually all of your package problems. I love the FreeBSD kernel, but wouldn't think of using any system that doesn't match up to Debian in terms of package management. And none that I know of do, so far.

      To be honest, I've tried FreeBSD (really tried),and and really want to like it, but coming from a Debian background, FreeBSD's package management is much too primitive to consider.

      Debian not only automatically downloads and installs packages along with their dependancies, it will set up virtuall all programs properly - they run out of the box. Daemons come up as soon as you install them, and reload when upgraded. Upgrading a particular package will upgrade dependant packages. Installing an X app will automatically add it the menus in almost all window managers available. Uninstalls go just as easily. Conflicting packages are managed, so that your favourite pager is known, even with many different paging programs installed. RPMs can be imported into the system, and there are importers for other standard packages like gtk/windowmaker themes (and CPAN too, if I recall correctly).

      What else? CDs can be built automatically from the packages on your system (using an add-on package), kernels can be automatically built and patched. Hell, that's enough. You should be convinced by now. In fact, I really can't believe that Debian hasn't replaced RPMs and PKGs by now. I looked up the BSD family's new OpenPKG system with hope, expecting them to have at least included debian's features, and perhaps expanded on them, but no. It's still the same old last generation stuff. Which, frankly, is just crap after using Debian. Did I mention that the latest version of Debian (the current one, in FreeBSD terms) has over 8000 packages available? Gotta love it =)

      In short, if package management is a priority for you, then use Debian - it's that simple.

    7. Re:ports by Anonymous Coward · · Score: 0

      Unfortunately, I don't think that RPMs contain enough information to let apt do it's thing properly.

      Still, at least people can get used to the interface before they switch to Debian ;)

    8. Re:ports by Anonymous Coward · · Score: 0

      I've used the ports in FreeBSD. What a great system!

      It will download and install it for you. If there are any dependecies, it will download install those too.

      RPMs can't compete with that! Have you ever seen an RPM system automatically download and install any dependecies?

    9. Re:ports by Arandir · · Score: 2

      apt-get is the best there is when it comes to precompiled binaries for the generic i386. But this is the world of Open Source. You have the source code, so use it! With source code you can optimize all the software for YOUR hardware, configure the software how YOU want it, etc. The best tools for upgrading software from source is ports.

      Binaries are great for quickly getting a system up and running. But once you've got the system up and running, switch to source code.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    10. Re:ports by damiam · · Score: 1

      apt-get -b source package

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    11. Re:ports by CatherineCornelius · · Score: 2
      Binaries are great for quickly getting a system up and running. But once you've got the system up and running, switch to source code.

      This works well for a full time sysadmin, on a well resourced system, but on this Thinkpad I've got far better uses for the 2GB hard drive, and far better uses for my time. There's nothing to stop me doing a bit of source hacking on the bits I'm really interested in, of course.

    12. Re:ports by Arandir · · Score: 1

      portupgrade -P package

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    13. Re:ports by damiam · · Score: 1

      Your point is? They both work. I'm just saying that, while the ports system may be nice, it's not the only good way to upgrade your system and it's not by itself an overpowering reason to use BSD.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    14. Re:ports by Arandir · · Score: 1

      and it's not by itself an overpowering reason to use BSD.

      Does the converse also apply to Debian? Is apt-get an insufficient reason to switch? Of course the answer is yes, but I've run across too many Debian users who would argue otherwise.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    15. Re:ports by Anonymous Coward · · Score: 0

      rpm doesn't require packages either.

    16. Re:ports by krogoth · · Score: 2

      They have enough information to fail dependency checks :)

      --

      They that quote Benjamin Franklin on liberty and safety deserve neither.
  61. FreeBSD ports and Sorcerer by Shiny+Metal+S. · · Score: 2, Insightful

    So it's basically the same thing which Sorcerer wants to achieve, right? Than maybe Sorcerer should just use FreeBSD ports instead of reinventing the wheel?

    --

    ~shiny
    WILL HACK FOR $$$

    1. Re:FreeBSD ports and Sorcerer by neroz · · Score: 0

      They could perhaps use the FreeBSD implementation of ports, but if you actually look at it, it's written completely in makefiles. This is very nasty. Gentoo on the other hand, have implemented their ports system in Python, which is a very good choice IMHO, since it's easy for a large number of people to understand how everything works without having to submerge themselves in messy code for months on end. Also, just using the entire ports system from FreeBSD doesn't make sense, since it's tailored to FreeBSD (eg. patches to make things compile properly on FreeBSD are applied at compile time).

    2. Re:FreeBSD ports and Sorcerer by cymen · · Score: 1

      Well Sorcerer couldn't just use the FreeBSD ports because they have the specific patchs for FreeBSD. I assume you know that but just pointing out one downside. One you have to change all the patches to your system there isn't much left. Maybe it just depends how you look at it. Anyway, apparently Sorcerer decided to go from scratch and I don't really find that too surprising.

      The interesting thing out there is OpenPorts. I don't really know what they plan on doing besides guessing from the name but it sounds good to me. Hrm... I'm not finding a page for the project.

    3. Re:FreeBSD ports and Sorcerer by Arandir · · Score: 1

      There is an openpackages project that means to integrate all the BSD ports, so that there won't be a separate ports tree for OpenBSD, NetBSD, FreeBSD, and Darwin. It's open for Linux participation.

      As I understand it, the underlying system will be the same for all participants, but individuals platforms would have to maintain their own patches.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    4. Re:FreeBSD ports and Sorcerer by neroz · · Score: 0

      OpenPorts appears to be dead in the water unfortunately. It really would have been nice to have a unified ports system between the three BSD systems... Personally I think they should adopt the use of Portage, which is written in Python and currently in use by the Gentoo distro. Results in a very clean package system in comparison to hordes of makefiles.

  62. Re:TROLLS DEMAND EQUALITY by poemofatic · · Score: 1

    sounds like a great idea.

    --

    When in doubt, have a man come through a door with a gun in his hand.

  63. Re: I actually have seen the pattern.... by Pengo · · Score: 3, Funny


    Mandrake/RedHat -> Debian/Slackware -> *BSD -> Debian

    ;-)

  64. Re:the kernel? my god man by Anonymous Coward · · Score: 0

    >but nobody controls the pot.

    Which is good. If all the pot was in a central storage, what would happen if the police had a razzia!? My god [sic] man, stop and think.

    (It's funny, laugh.)

  65. Original idea was Debian OpenBSD by Anonymous Coward · · Score: 3, Interesting

    The original proposal was for Debian OpenBSD:

    Debian OpenBSD topic

    Debian OpenBSD txt

  66. Not so far fetched a thought.. by Anonymous Coward · · Score: 0

    DebiaNT is not so far fetched. It may even be useful to have all Debian packages ported to e.g. CygWin running under Windows to e.g. accelerate the development of POSIX and X on Windows. Having POSIX and X on Windows is useful also because it works as a bridge between the Open Source environment on *NIX platforms and Windows. Having Debians package system working on Windows/Cygwin too would make it even easier to use and upgrade the CygWin packages. It would also be easier to manage CygWin for the users, which now has a reputation of being a large monolithic chunk.
    Think Embrace and extend strategy towards Windows!

    Mvh.
    Nils Ulltveit-Moe

    1. Re:Not so far fetched a thought.. by ecc0 · · Score: 0

      ...And it has happened. Debian GNU/w32

  67. Re: I actually have seen the pattern.... by Anonymous Coward · · Score: 0

    *BSD -> Debian

    Never. Ever.

  68. Re:TROLLS DEMAND EQUALITY by Anonymous Coward · · Score: 0

    I support it.

  69. So wait...let me get this straight... by 8bit · · Score: 1

    NetBSD runs on everything, right? Hardware-wise at least.

    Now Debian runs on everything? Kernel-wise at least, and with NetBSD, hardware-wise too? Freaky stuff...

    --

    --Roy
  70. Re:Mirror of wonderful post by Anonymous Coward · · Score: 0

    Boss: "MySQL/Apache/Linux/(Your favorite OSS project here) just choked and threw up on itself."

    Geeky OSS Admin: "Oh well that's because [yadda yadda yadda]. It's your fault. Jesus Christ, RTFM!!"


    Boss: [ODBC Microsoft Access Driver]General error Unable to open registry key Temporary (volatile) Jet DSN

    MSCE Admin: That's an occasional bug when using ODBC for Access, I told you we should reboot the server every day!! br>

  71. Perfect time to move from DEB to RPM by Anonymous Coward · · Score: 0

    Since even BSD is moving to RPM and RPM is the mandated package system for Linux Standard Base, this would be a good project for Debian to test the waters of current technology. It would allow Debian to transition to RPM on this hybrid testbed, working the kinks out in the process. This would allow the work to go forth without disturbing the current main Debian branch. Then when the time was right, the overall switch could be made smoothly to RPM. Now's the time to act!

    1. Re:Perfect time to move from DEB to RPM by Anonymous Coward · · Score: 0

      RPM is a linux bug

  72. What came first, the GNU kernel or linux? by 3seas · · Score: 2

    I'm a bit confused here. Didn't the GNU community (what is pretty much what debian is) show it's openness to other kernels when it accepted the linux kernel while continuing on with the original GNU Hurd system? Even knowing it would slow down the progress of the Hurd?

    I'm confused because the listy of reasons seem to suggest that it was in accepting the Hurd that states Debian is open to other kernels.

    And even the Hurd is open to different micro-kernels! Mach and L4 are current micro kernel use efforts.

    1. Re:What came first, the GNU kernel or linux? by SpinyNorman · · Score: 2, Informative

      Linus's kernel and the GNU project are two seperate things. GNU predates the Linus's kernel and was always meant to be a complete Unix implementation - both user tools such as gcc, glibc, emacs, tar, ftp, etc, etc, and the kernel HURD. The timing of it was that the GNU project was pretty much complete excepting HURD while in parallel and independently Linus had started his kernel project and it had got to the point of being usable.

      My history is a bit shaky here, but I think it was the Slackware team which first made the unholy alliance of the GNU tools and Linus's kernel, and released it as a Unix distibution. I think Linus may have coined the name "Linux" a bit earlier for the combination of his kernel and a small set of GNU tools.

      I think that Debian is more of a Linux distribution than a GNU project - even though the GNU project is what make Linux possible, they've never actually put out distributions of their OS themselves. But of course Stallman would like them to get credit for the fact that the only part of Linux that is Linus's is the kernel (a miniscule part of what's in a "Linux" distribution).. hence the GNU/Linux and GNU/HURD pedantry which is quite reasonable apart from Stallman's initially obnoxious way of handling it.

    2. Re:What came first, the GNU kernel or linux? by ceswiedler · · Score: 3, Informative

      Well, no, it was Linus himself who first paired the kernel with GNU tools. He developed it using GNU development tools on Minix and then Linux itself once it was usable, and ASAP he had the standard GNU toolset compiled and running on his own box.

      Perhaps Slackware did indeed release the first distribution; but from the start, GNU was used on Linux. I imagine that the 0.1 release had some mention of "BTW, if you want to actually DO anything, go get the GNU stuff..."

    3. Re:What came first, the GNU kernel or linux? by Cro+Magnon · · Score: 1

      I think SLS was the first Linux distro. Slackware was based on SLS, and is the oldest surviving distro.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  73. Re:the kernel? my god man by Anonymous Coward · · Score: 0

    Sounds to me like you're illustrating what he's been talking about.

  74. Re:ROFL by Anonymous Coward · · Score: 0

    Linux has stolen bits of FreeBSD code before. They got into hot water though because they didn't include the BSD license text.

  75. There is no need whatever for something like this by Anne+Thwacks · · Score: 1
    NO, actually there isn't.

    If you need to run Linux stuff on *BSD, you just install it and run it.

    All the *BSD's have the ability to run Linux stuff through a hack to the loader (Obviously, its not officially called a "hack"). It works fine. There is no obvious performance penalty, and the stuff runs (although, I have to admit, it took a bit of work for me to get Star Office to work on one of the BSDs). NestCrap works as well as it does under Linux :-(

    AFAIK, the ports/packages systems include DB2, Oracle, Star Office/Wordperfect, etc, and they are as easy to install as native BSD stuff in principle.

    But IBM, if you are listening, Id still rather PAY for native BSD DB2 than use the free hack.And Larry Ellison, if you are listening: Up Yours

    --
    Sent from my ASR33 using ASCII
  76. Re:the kernel? my god man by jelle · · Score: 1

    "One of the major problems with Linux is *that* it's every yahoo for himself"

    And I think that's good think, much better than a hurdle of people who act as if they are god and know everything better than anybody else.

    10-20 people cannot know it all, neither can they force application programmers to stick with just this library, or that that program is 'bad for users because it uses a different library that nobody else uses'.

    I'm one of those users that likes to decide himself what is best for him, I don't need a team of guru's to do that for me.

    " or a standard place to put software"

    That is not inherent to the development method of the GNU+Linux-based OS. I'd say that HPUX has a pretty tight control with a very limited development group contributing. Still, there are binaries in /etc/ (grep anybody?), and the init.d scripts are in /sbin (s_bin_!!).

    "Just as no one can take control of the whole thing and fix it"

    Yes you can, and I can too. In my sytems, everything is perfect the way I want it, the whole thing is fixed. Crap stays out, good stuff goes in. I decide, and nobody else.

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
  77. Re:Mirror of wonderful post by cmkrnl · · Score: 1

    Excellent mod this AC up, post of the week.

    Sir, please take a bow. I dont think I could have put it anywhere near as succintly.

    For the average Open Sores Zealot, "there are none so blind as those who will not see. "

    Curmudgeon

  78. Re:ROFL by SubtleNuance · · Score: 2

    Just remember, Adolf Hitler was a socialist.

    Yes, and your point? Timothy McVeigh (whatever) was a Christian, Oliver North was is a Republican and John Locke was an Anarcho-Syndicalist.

  79. Re:Mirror of wonderful post by Anne+Thwacks · · Score: 1
    I think you've lost the plot here - the server (as its running OSS) is in all probability a used 486, on the end of a 300 baud modem. When overloaded, it delivers an error message.

    If it was an MS operation, it would be on $10k worth of hardware, connected via T3. When over stressed, it would collapse in a heap and wait for a re-boot.

    In all known tests, OSS delivers more power on less kit, and fails cleaner, or someone was bribed.

    If you can read this, thank a troll.

    --
    Sent from my ASR33 using ASCII
  80. Re:the kernel? my god man by DrSkwid · · Score: 2

    Guess how we ended up with so many different *BSD versions?

    As the saying goes :

    two great things come from Berkley, LSD and BSD

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  81. What next? by archen · · Score: 2, Funny

    Does this mean that the "BSD is dyeing" guy is going to finally update his message to include Linux?

  82. ^ Mod this up by biftek · · Score: 0, Offtopic

    That would have to be probably the best bit of writing i've seen on slashdot for a while. I got strange deja vu to some other book i've read (no, not copied text, just the idea), but can't remember the title. Oh well.

  83. Re:That is why Microsoft gets all the customer bas by Anonymous Coward · · Score: 0

    > I don't need a unix timesharing system to listen to mp3s and use netscape.

    Yes you do. if you want to do both at the same time.

  84. Re:the kernel? my god man by Anonymous Coward · · Score: 0

    So many versions of BSD vs. Linux distros?

    Linux = 100+ distros
    *BSD = FreeBSD, NetBSD, OpenBSD, OS X Xmach.

  85. Re:ROFL by Anonymous Coward · · Score: 0

    What's wrong with Oliver North?

  86. my thoughts on a distribution by scrytch · · Score: 2

    I once thought of making a Linux distro -- yeah, everyone has -- but short story shorter, I don't have that itch to scratch anymore, since I have sitting in front of me a box that's running just Win2k. I got cygwin, liked it for a while, and have grown to hate it. Slow, buggy, and now unreliable in config -- make stopped working, some weird interaction with shell quoting. Make is kinda important yunno. The DLL that every last damn cygwin program needs is also GPL'd, which ironically might violate the LGPL for a lot of binutils. Discouraging commercial apps from using cygwin might be A Good Thing anyway, since it's not a paragon of security (it uses a shm segment to keep state like fd's). So I'm switching to MinGW, which is much nicer in many ways, but it has an even worse system of distribution than cygwin's rather unimpressive kludgy installer (which for starters is impossible to use without a mouse)

    So I am wondering, what about porting something like BSD ports or Gentoo's portage or Debian's apt to MinGW? They're all ostensibly architecture-neutral, right? Personally I am leaning toward ports, because it uses the right language for dependency checking (make), it doesn't require packages (great for embryonic distros that don't have everything in packages). Portage OTOH looks like it has transactional features ports does not. I don't want to get mired in trying to design The Package System To End All Package Systems ... I would like to know if anyone else is working on such a thing for cygwin and/or mingw though.

    --
    I've finally had it: until slashdot gets article moderation, I am not coming back.
  87. Noooooooo! Stay away! by The+Ape+With+No+Name · · Score: 2, Troll

    I am not a NetBSD user, but I love FreeBSD like Madonna loves dick. Debian's pkgs are interminably behind the curve relative to the rest of Linux-land and this would only serve to slow down NetBSD's acceptance. As far as BSDs go, NetBSD aims for hardware-indpedence/multiple platform acceptance. It is already behind the curve as far as pkgs go. The Debian "keep it stable at the cost of progress" mentality might hurt NetBSD. Please keep these people away. They might come after FreeBSD and really dick up things. Luckily, OpenBSD has Theo -- who is just plain mean as shit -- to protect the very important security work that is done over there. I don't see Hubbard as such a crusader to stop the "everything-that-is-bad-about-linux" crowd from poking their heads in.

    --
    Comparing it to Windows will be a moot point, since El Dorado is going to have a 40% larger code base than XP.
    1. Re:Noooooooo! Stay away! by faedle · · Score: 3, Insightful
      I'm sorry if keeping it stable is such a bad thing for you. Fortunately for people who's jobs depend on reliability and stablilty of the systems they maintain, there are people like the Debian developers who think that keeping it stable is a Good Thing.

      How quickly we forget that stability is how many of us have sold Linux and *BSD to our employers, and that sudden rash changes and stability problems can leave those who require stability out in a lurch.

      I see Debian's methodical approach to "current" as a good thing. Debian is about choice: if you want to be on the bleeding edge, please run unstable, we need the beta testers. If that's not your game, here's the stable tree. If you're really anal (or demented), here's the last version with security patches.

      Sounds like a win for everybody. NetBSD gains more users (those who happen to get off on apt-get), Debian gets to work on porting to other kernels (a major cornerstone of the Debian project's defined goals), and everybody gets more choice.

      Stay away from system administrators who think that the "latest" is always the "greatest."

    2. Re:Noooooooo! Stay away! by The+Ape+With+No+Name · · Score: 3, Insightful

      My experience with STABLE and Debian GNU/Linux is that it is an outdated tree. FreeBSD pkgs, again in my experience, are right where they need to be, not outdated versions of common apps.

      --
      Comparing it to Windows will be a moot point, since El Dorado is going to have a 40% larger code base than XP.
    3. Re:Noooooooo! Stay away! by Anonymous Coward · · Score: 0

      Your comment seriously flawed, probably due to ignorance. Ever heard of debian/testing?

    4. Re:Noooooooo! Stay away! by drinkypoo · · Score: 1
      I am not a NetBSD user, but I love FreeBSD like Madonna loves dick.

      What are you trying to say here, that you use both FreeBSD and linux?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Noooooooo! Stay away! by faedle · · Score: 1

      One man's "outdated" is another man's "stable."

      'Nuff said.

  88. Re:That is why Microsoft gets all the customer bas by superpulpsicle · · Score: 0

    This is not a video game. OSes are alot more complicated. I am saying the unix-world port software as common as getting coffee in the morning. They overlook the big picture where support, patch releases and all these non-technical customer-based issues get exponentially multiplied. Why do I got the feeling I am replying to someone who used to install TOMATO and POTATO versions of linux.

  89. Why is this modded a 5? by Anonymous Coward · · Score: 0

    I guess of the three moderators all are bsd lovers? Because if they were not then they would say this is just trolling which is it.

    Sorry but linux users are not "migrating to bsd".
    You cannot even compare the linux user base to the bsd user base. Linux has many many many more users and servers out there. BSD is a fine system, but lets not kid ourselves, besides a couple of popular web sites linux(right or wrong) is the open source OS of choice for the majority. This is not even a matter of debate.
    Unless of course every OS survey ever done is completely wrong. Doubtful.

  90. Re:ROFL by Anonymous Coward · · Score: 0

    Yes, and your point? Timothy McVeigh (whatever) was a Christian
    What are you smoking... McVeigh is not a Christian - by his own words. He described himself as an agnostic or something. Well of course there is an excuse for not knowing that. Considering the quality of the media we are forced to use...

  91. Re:ROFL by Anonymous Coward · · Score: 0

    Oliver North - Iran Contra, and the CIA / Reagan / Bush / Negroponte death squads in Central America in the 80s.

    Is that enough?

  92. Re:the kernel? my god man by kan · · Score: 1

    Actually, the number of committers in FreeBSD is close to 300. But do not make mistake thinking that the number of committers represents the number of actual developers. FreeBSD has a GNATS system and and a number of developer-oriented mailing lists where everyone is welcome to submit patches. Think about the whole bunch of BSD nomads from Japan, all hiding behind handful of Japanese committers as an example.
    Besides, FreeBSD is using a lot of "contributed" software, take 'bind' for example. BSDs only provide a glue to integrate such a software into the base system but try hard to feed all other changes back to original vendor. This allows them to minimize divergence with an 'official' package versions and eliminate associated support problems.

  93. cygwin by Anonymous Coward · · Score: 0

    Actually, there already is Debian cygwin. :-)

    why..

  94. This is so shortsighted! by 2nd+Post! · · Score: 3, Interesting

    What happened to the concepts of diversity, hybrid vigor, competition, and cooperation?

    With Microsoft we get a monoculture.

    Are you suggesting the same for all other OSes?

    If nothing else this project encourages and explores compatibility issues, source examination, bug catching, performance tuning, and a bunch of other things, if only because a new, fresh, set of eyes (Debian) is looking at old things (BSD), and the other way around, BSD people looking at Debian things.

    This cross pollination can have so many surprising and unexpected benefits too. Like the fact that if the kernal is BSD and the userland is Debian... it means you could, besides a little project called Fink, place an entire Debian OS layer on top of Apple's Darwin or Apple's OS X.

    Then there is the ports system, which sounds very good to me. It's currently a BSD thing, but there's nothing stopping it from running on top of the Debian-netBSD distro, with work, and therefore stopping it from working on GNU-Debian with just a little more work, with 'work' and 'little more work' being subjective here.

    These are just obvious speculations on my part. Many more advantages can be found, I'm sure, of this type of project.

  95. Re: I actually have seen the pattern.... by Anonymous Coward · · Score: 0

    That's like

    torch/fire place -> oil lamp/candle -> electric light -> oil lamp

  96. Re:Not this NetBSD user... by Anonymous Coward · · Score: 0
    Open Source, even though GNU zealots will not agree. Fellow BSD'ers will soon recognize the errors of their ways and join ranks with the Apple crowd.

    Errors of our ways? Join the Apple crowd? Who are you kidding? The NetBSD project is going strong as ever and is doing just fine, thank you - with or without Apple.

    Powerful inexpensive yummy hardware - G4 PowerMacs trump x86 by a long margin and cost much less than underperforming but expensive SPARC, MIPS and the PeeCee user's Holy Grail of DEC Alpha, which was intended to run WinBlows from the beginning and is dying anyways.

    The NetBSD project prides itself on portability and eschews focus on any one particular platform (unlike Linux, which seems to be obsessed with ix86 and PPC). Which archs does Darwin run on anyways? :-P

    Regarding your statement about SPARC, MIPS and DEC Alpha; all of the above are far superior to Apple Macs implementation of PowerPC.

    64-bit memory path? Slow I/O? Non-ECC main DRAM and cache? Hardly high-performance and worthy of comparison to SPARC/UltraSPARC, SGI MIPS or DEC Alpha.

    BTW, as other posters have stated, DEC Alpha was NOT designed to run Windows NT but its own VMS operating system.

    Get a clue before spreading more Apple FUD.

    Many Free/Open/NetBSD users are coming to that conclusion as are many Linux users, beset with flaky kernels and horrible OS packaging.

    Whilst I cannot comment on Linux not having used it since 1.3, I can wholeheartedly state that having used OS X 10.1 extensively, I see absolutely no reason to switch over to OS X from NetBSD.

    Personally I welcome the Debian project to the BSD community. To me, their GNUisms are much less objectionable than the Apple/Mac "based on Unix" hype and their decision to pursue a BSD-based distro reinforces their reputation for quality.

  97. Re:ROFL by Anonymous Coward · · Score: 0

    idiot. the code in question (well, actually it was a header file, which is an interface and hence not copyrightable in the US) was never part of the linux kernel.

    Linux does use the BSD PPP compression code, however. It is properly attributed.

  98. Re:the kernel? my god man by Anonymous Coward · · Score: 0

    So how many binary incompatible versions of BSD vs. Linux distros?

    Linux = 2 (libc5, libc6) and you can easily have both installed at the same time.

    *BSD = 6: FreeBSD, NetBSD, OpenBSD, BSD/OS, OSX, Xmach. There are emulation layers for Free on Net, and for Free and Net on Open. OSX is off in its own little world, and I have no idea about emulation for Xmach...

  99. Re:frist by Anonymous Coward · · Score: 0

    Because you're too stupid to figure it out.

  100. Re:the kernel? my god man by haggar · · Score: 1

    However, I do have to take issue with the original poster who gave no reasons (good or bad) as to why he would like to have the Linux kernel with the FreeBSD userland. Why are you hell-bent on protecting his non-argument?

    --
    Sigged!
  101. Cool by zak+mchacken!! · · Score: 0

    Now I can get Coldfusion to run on NLEITNBUSXD (thats my name for it).

  102. Re:the kernel? my god man by jelle · · Score: 1

    Sounds like nothing different than the various gnu & linux mailing lists and the Debian maintainers combined.

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
  103. Re:the kernel? my god man by jelle · · Score: 1

    "Could you tell the slashdot editors that?"

    Are you making a point or enlisting my effort? If the latter, maybe a fork is the only solution (freedot.org? opendot.org?). If the former, your point is as strong as the repeated stories and MS-paranoia we regularly see here.

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
  104. Re:ROFL by Anonymous Coward · · Score: 0

    Yes, 3.5 inch floppies are outrageously substandard media by any god fearin' right-winger's definition.

  105. Re:the kernel? my god man by kan · · Score: 1

    It makes a world of difference when you are trying to implement something which touches both kernel and userspace at the same time, just as an example. Good luck finding central point of contact to discuss your patches :)

  106. Your *linux concerns are trumped by BSD by Anonymous Coward · · Score: 0

    You wax poetically about how 'linux has better desktop support', yet you blissfully ignore that BSD has the BEST desktop support.

    Mac OS X.

    BSD has done what *linux has not. Offered a UNIX OS that consumers will actual BUY.

    1. Re:Your *linux concerns are trumped by BSD by m_ilya · · Score: 1

      Have you bothered to read my comment? It was about FreeBSD and Debian Linux.

      --

      --
      Ilya Martynov (http://martynov.org/)

  107. Poor parentage by Anonymous Coward · · Score: 0

    Great...a version of BSD that no-one uses, coupled with the elitist asshole version of Linux that always 2 years out of date. I can't wait to see this...

  108. Re:unfortunatly... by Anonymous Coward · · Score: 0

    *WHO* uses bsd is whats important. Power to SERVE! bsd has a huge following in the serving community. For the desktop system, I believe that linux is stronger and makes more sense, but if I needed to serve 1000s of users per day or even hour(or minute), i wouldn't hesitate to choose bsd

  109. A plethora of package formats... by Anonymous Coward · · Score: 0

    I know I'll get flamed for saying this, since my post will be full of illogic, BUT...

    (e.g. anticipated reply "what crack are you smoking?" :) None, I'm strange enough without substance abuse!!)

    I'm not going to mention the technical merits of Debian, they have enough advovates!

    I broadly support the notion of open source, but it seems a fair percentage is taken up by duplication of efforts.

    A fair proportion the linux crowd have adopted RPMs because redhat has corporate mindshare. Like it or not but Oracle, IBM and other big-guys are likely to agree on RPM for distribution. It's *easy* since they can form an support alliance with Redhat, whereas debian is a collective of volunteers.

    Now everyone involved in a packaging responsibility will argue the merits of their system be it: BSD ports, deb, rpm, tgz, fink, openosx... (or in the Java universe, Java webstart!)

    I'm not here to debate the merits of each, since no one will win that argument.

    But it strikes me that the man in the street cares about ease of installation and not what distribution they happen to stumble across.

    I read an interview where one of the BSD guys said that it would be nice to integrate the various ports trees of NET/Open/FREE, while keeping the distinct kernel. A logical extension of this would be to embrace their open source linux cousins too.

    There's a project at openpackages.org which has similar thoughts to me.

    What is missing is consensus. How about a summit for all you open source packaging gurus to consider a unified packaging model?

    My dream...

    Now maybe you can all have your own quirks underneath, but I dream of a day were installing software (source or binary) is seamless.

    Pick a website, click install and voila!

    Instead it seems you have package maintenance in oh-so-many-ways be it Net/Open/FreeBSD, Darwin (OSX), and all of the Linux distros.

    Maybe then we can have a redhat/debian/*BSD etc core CD and a few other CDs full of open source goodies that will install on all the major unices regardless of flavor, and hopefully architecture (src compile if desired). Too hard?

    Am I advocating a lack of choice? Maybe, but only to assist on the real focus, writing beaut software.

    Good night and cheers!

  110. Re:The former, fork slashdot. by jelle · · Score: 1

    Doesn't sound bad. Inside of the discussion website, you can have 'virtual communities' in which the members rate, accept, and possibly reject stories.

    Hmm, technically almost the same result should be possible inside of /., simply by having multiple sets of editors, and letting users 'subscribe' to particular groups of editors, or maybe a mode 'show me only stories accepted by at least three editor groups', and 'don't show me any story that has been reported dupe by a reader', and 'don't show me stories that match the following regexp'

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
  111. Re:Transition (FreeBSD vs. Debian wrt packages) by d^2b · · Score: 1

    I too run FreeBSD and debian/linux.

    I would say package/port breadth is a tossup.

    But I really like the separation of the upgrade
    process into core and ports that FreeBSD has.
    I have never made my machine unusable using ports. I have had some close calls with apt.

    Also, my limited experience is that it is easier
    to wedge things with apt-get than with ports
    because problems show up during the build process
    with ports, and the install process with
    apt.

    You may cry that that is an unfair comparision
    since I could build packages from source on debian. But that is not the typical user experience.

  112. Cool by Anonymous Coward · · Score: 0

    This is the Coolest Thing since Debian GNU/Hurd. I love Debian. The is nothing that one could compare to it. Corel and Storm knew why they used Debian as a base, because it is simply the best and that is also the reason they failed, since you can't top it. And now another kernel. Thanks to all the developers who made and make Debian happen. Cheers

  113. An alternative to dselect by _Laban_ · · Score: 1

    dselect is pretty hard to get started with, but it works fine when you get used to it (as most software). But I can really recommend console-apt which is a replacement based on an ncurses-interface. I use it all the time even though I know dselect really well.

    Give it a try if you don't like dselect:

    console-apt

  114. So does this mean by Cro+Magnon · · Score: 1

    that I can use apt-get on my toaster?

    --
    Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  115. Re:the kernel? my god man by Anonymous Coward · · Score: 0

    Ever heard of Linus Torvalds? Oh, and for the v2.4 kernel it's Marcelo Tosatti, for v2.2 it's Alan Cox. For v2.0, it's yours truly.

    So do you still get lots of requests for Debian Kernel Bugs?

  116. Re:the kernel? my god man by tao · · Score: 1

    Not really, something I consider a good sign. I've applied about 15 bugfixes since December 2000, and intend to add some 4-5 more before the release of 2.0.40.

  117. Re:the kernel? my god man by tao · · Score: 1

    Well, I don't know why he'd want that. Probably personal preference. Maybe he has hardware not supported by the FreeBSD-kernel, maybe he wants some feature of the Linux-kernel not available in the FreeBSD-kernel. But is that really interesting?! It can be done, the code is open-sourced, and a real hacker doesn't do things out of real use anyway, but out of the hackvalue.

  118. Re:The former, fork slashdot. by kiwipeso · · Score: 0

    Yes, the trolls had a good idea about a party system.
    I think it would be best run as an extension of friends and foes.
    Troll party, linux party, apple party, microsoft party, netscape party, liberty party, bsd party, etc.

    It would save a lot of people the nuisance of Jon Katz, repeated stories of minor linux events, trolls and the like.

    --
    - Kaos games and encryption systems developer
  119. Re:TROLLS DEMAND EQUALITY by Anonymous Coward · · Score: 0

    In an interesting development over at slashdot, Deviant has been ported to NetTaco. This involves inserting the undigested kernels of corn from Taco's shit into the snot dribbling from his nose.

    EDITORS: HURRY UP! by Anonymous Coward (Score:-1)

  120. jaja by Anonymous Coward · · Score: 0

    windows xp sucks