Slashdot Mirror


FreeBSD 10.2 Released

moderators_are_w*nke writes with news that FreeBSD 10.2-RELEASE is now available. Here is the download page, the release notes, and release errata. Features highlights: The resolvconf(8) utility has been updated to version 3.7.0, with improvements to protect DNS privacy. The ntp suite has been updated to version 4.2.8p3. A new rc(8) script, growfs, has been added, which will resize the root filesystem on boot if the /firstboot file exists. The Linux® compatibility version has been updated to support Centos 6 ports. Several ZFS performance and reliability improvements. GNOME has been updated to version 3.14.2. KDE has been updated to version 4.14.3.

103 comments

  1. /firstboot by Anonymous Coward · · Score: 0, Funny

    /firstboot

  2. Still no 64-bit Linux support? by the_humeister · · Score: 2

    Oh well. I use it for only ZFS anyway.

    1. Re:Still no 64-bit Linux support? by moderators_are_w*nke · · Score: 4, Informative

      It's in -CURRENT, not sure whether it will make in to -STABLE before 11-RELEASE.

      --
      "XML is like violence. If it doesn't solve your problem, use more." - Anonymous Coward
    2. Re:Still no 64-bit Linux support? by jandrese · · Score: 1

      IIRC the patch came in a bit after the cutoff for 10.2. It will probably be MFC for 10.3.

      --

      I read the internet for the articles.
    3. Re:Still no 64-bit Linux support? by Anonymous Coward · · Score: 0

      You don't need support for 64-bit Linux in FreeBSD ABI to run ZFS on both platforms.
      Just don't upgrade the version of ZFS/ZPOOL on FreeBSD beyond what the older one on Linux can support.

      And what on Linux are you looking to run on FreeBSD that isn't already in FreeBSD ports/packages?
      And could you find alternatives, run it in a VM under FreeBSD, or do without?
      Those are the questions.

    4. Re:Still no 64-bit Linux support? by Anonymous Coward · · Score: 0

      When I looked into FreeBSD for some HPC applications it came down to missing support from MATLAB which only supports Linux, and they have deprecated 32 bit support for some time and removed it recently. Same thing for many other binary-only applications.

      I guess Steam has the same issue.

    5. Re:Still no 64-bit Linux support? by Blaskowicz · · Score: 1

      No, Steam is in 32bit and 32bit is the norm for games. Some of the appeal is to run a few 10 to 15 year old Valve games, after which I don't know what's worth playing.

  3. Zombie Apocalypse by Anne+Thwacks · · Score: 0

    Yes, they really are rising from their graves. Netcraft confirms it!

    --
    Sent from my ASR33 using ASCII
    1. Re:Zombie Apocalypse by Anonymous Coward · · Score: 0

      I understood that reference.

    2. Re:Zombie Apocalypse by moderators_are_w*nke · · Score: 1

      I was hoping for some Netcraft comments when I submitted it.

      --
      "XML is like violence. If it doesn't solve your problem, use more." - Anonymous Coward
  4. Re:Ob by jandrese · · Score: 4, Informative

    No, although there is a package called uselessd that provides enough systemd hooks to get Gnome running if that's your thing.

    --

    I read the internet for the articles.
  5. Really like FreeBSD by Anonymous Coward · · Score: 5, Interesting

    It's a real pity that FreeBSD and the BSDs in general don't get more love from Slashdot. Linux seems to have stolen the thunder from the BSD camp, but in all honesty, FreeBSD rocks. It makes a far better server than Linux for the vast majority of cases. I used to run BSD servers, both FreeBSD and BSD/OS back in the day. Never, ever had an issue save for HW failures. Cannot say the same for Linux on identical HW. FreeBSD handles load that bring Linux to its knees. I've always agreed with the statement that "Linux is hacked together, while FreeBSD is engineered". In general, I think the BSDs are better written pieces of software.

    1. Re:Really like FreeBSD by Anonymous Coward · · Score: 2, Insightful

      To be fair, they can both "serve" various use cases pretty well. Though FreeBSD is more "service" centric than Linux's "user" centric. However FreeBSD (having come out from all of the post 4.x SMP development years) is now really beginning to invest and shine in some of Linux's traditional "user" areas and is running on things like ARM, RPi, etc.
      And yes, the "hacked" versus "engineered" thing is definitely true, and it's the reason I no longer use Linux, I simply can't afford the extra time to deal with having to manage and deal with the constant churn and battles and disappearing acts in "Linux distro land".
      With FreeBSD I have one product from one place... kernel, userland, filesystem, networking, ports/packages... and it's been there that way all along ever since before Linux existed.
      I'm happy with that.

    2. Re:Really like FreeBSD by Anonymous Coward · · Score: 3, Insightful

      OP here. Great comment, and I agree. While I think Linux makes a great desktop OS, I'm a firm believer in BSD on the server side. I've run BSD-based firewalls/proxy servers and BSD-based Web servers and I really love how simple BSD makes config files. All in one place. Linux, as you note, depending on the distro, in several places.

      Right now at work, I have Linux servers in certain roles (CentOS for PBX and Debian for Web server) and the config files are Greek compared to FreeBSD and OpenBSD's simplicity.

      My next home-based machine is going to be a Chromebook because that is really where Linux has shined on the desktop. Hidden behind a veil doing one thing well. Don't get me wrong, I'm not bashing Linux as a whole, but as a sysadmin, the BSDs have proven themselves to me in ways the Linux distros have not. I've often said that if I ever ran my own company, I would have BSD in the server room and Linux on the desktops. I've seen this very setup before where a friend works and everyone there seems to really like how it all works.

    3. Re:Really like FreeBSD by Anonymous Coward · · Score: 3, Insightful

      I ran FreeBSD servers for a few years, but when Linux got journalled filesystems, an O(1) scheduler and real threads, it just made Linux better. Plus much better hardware support.

      I know FreeBSD eventually addressed much of that, but just too late.

    4. Re:Really like FreeBSD by walterbyrd · · Score: 2, Interesting

      Agree: BSD is a far better server than Linux. More stable, more standard, better engineered.

      Also, unlike Linux, BSD is still values POSIX, and UNIX philosophy.

    5. Re:Really like FreeBSD by Bengie · · Score: 2

      I didn't live through it, but based on what I've read and watched about the evolution of FreeBSD, they got set back for a long while from bogus legal issues and a resulting anemic community. It's well engineered base has allowed it to quickly catch up and is now starting to surpass Linux in *some* ways. While FreeBSD is lacking in some ways like a large driver portfolio and mind share of the popular crowd, the fundamental parts of the OS are starting to set the bar for high performance and stability. FreeBSD already has much superior documentation, but there is a new initiative to make it much better.

      With a good foundation of performance, stability, consistency, documentation, near seamless integration of stuff like ZFS and Jails, it is only a matter of time before it starts to get popular as an alternative. I hear PC-BSD 11 has made some huge changes to making the desktop experience even better than it already was.

      If there is anything that I've learned as a programmer it's that when something is well designed, it can change to meet a moving target of expectations without major changes. The Linux community has a whole has some ADD notion that tools are disposable and to replace them with the latest greatest tool. This is just a sign that no one put any thought into the original tool.

      FreeBSD implemented Jails back in 2000. Linux got Linux Containers in 2008, but still not nearly as good as Jails. Now Docker is gaining transaction. They really are all the same things. FreeBSD is getting work done to emulate Docker with Jails because Docker is only handles a subset of what Jails can do. Do it once, do it right, stop creating so many half-assed versions of the same thing!

    6. Re:Really like FreeBSD by Anonymous Coward · · Score: 0

      "FreeBSD handles load that bring Linux to its knees"

      I have a hard time believing this. The SMP support in Linux is far more mature than the BSDs.

      Or are you referring to running something on an old, single-processor desktop system?

    7. Re:Really like FreeBSD by DNS-and-BIND · · Score: 1, Insightful

      It's because a lot of BSD users are absolute jerks. They piss on anyone who isn't a part of their "ecosystem". A lot of people, including me, got scared away a long time ago due to this. Sure, I could use BSD, and it's evidently technically superior, but am I going to turn into one of THEM? Even if I don't, I'm still going to have to deal with these pricks on a daily basis while asking for support, and that's just too much. No way. Sorry, BSD.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    8. Re:Really like FreeBSD by TheRaven64 · · Score: 4, Interesting

      The Linux community has a whole has some ADD notion that tools are disposable and to replace them with the latest greatest tool. This is just a sign that no one put any thought into the original tool.

      (FreeBSD developer, so beware that there may be some bias here:) In my observation, there's a tendency for Linux developers to identify a problem and immediately implement and ship a solution. In the FreeBSD community, there's more of a tendency to identify the problem, step back and try to find a more general solution, then implement that. This means that Linux often has the solution right now, whereas FreeBSD often lags a bit, but when the FreeBSD solution exists it's a lot more pleasant to work with (compare kqueue vs epoll + timerfd + eventfd + ..., for example).

      Both approaches have upsides and downsides. I generally prefer the end result of the FreeBSD approach, but it still sucks when you're in the window (often a couple of years long) where Linux has a bad solution and FreeBSD has no solution at all.

      --
      I am TheRaven on Soylent News
    9. Re:Really like FreeBSD by TheRaven64 · · Score: 2

      I have a hard time believing this. The SMP support in Linux is far more mature than the BSDs.

      The fact that you'd make such sweeping generalisations implies that you don't know what you're talking about. The BSDs, in SMP support in particular, are far from homogeneous. FreeBSD began to move away from a giant lock around the entire kernel in 5.0 (2003), about the same time as Linux. Lots of work has gone on in various subsystems to introduce fine-grained locking. Linux tends to apply RCU in a lot of places (some where it's sensible, some where it isn't), which FreeBSD can't because of the patent issues, but benchmarks have shown that RCU scalability is decidedly nonlinear in a lot of places. FreeBSD has been used for a lot of network stack scalability in the last few years. I don't know exactly how Linux compares, but you may recall a job ad at Facebook that was posted a few months ago aiming to hire people to get the Linux network stack up to the same standard within 5 years...

      --
      I am TheRaven on Soylent News
    10. Re: Really like FreeBSD by Anonymous Coward · · Score: 0

      if you want to see the beacon of light out of the valley of cyberwar darkness, look to the horizon for the land of burroughs and their algol mainframes. icl and elbrus once had this too.

      until bell labs poisoned informatics with the concept of the portable assembly language. one kernel or driver bug opens the kingdom.

    11. Re: Really like FreeBSD by Anonymous Coward · · Score: 0

      bingo. os and compiler code should ideally be ages old and analyzed/proven secure by lots of different groups. new is a synonym for buggy-as-hell.

      donningy tinfoil hat i would argue tjis is the objective...

    12. Re: Really like FreeBSD by Anonymous Coward · · Score: 0

      so who pays for your FUD lobbing ? redmond or california ?

    13. Re:Really like FreeBSD by unixisc · · Score: 1

      It's a real pity that FreeBSD and the BSDs in general don't get more love from Slashdot. Linux seems to have stolen the thunder from the BSD camp, but in all honesty, FreeBSD rocks. It makes a far better server than Linux for the vast majority of cases. I used to run BSD servers, both FreeBSD and BSD/OS back in the day. Never, ever had an issue save for HW failures. Cannot say the same for Linux on identical HW. FreeBSD handles load that bring Linux to its knees. I've always agreed with the statement that "Linux is hacked together, while FreeBSD is engineered". In general, I think the BSDs are better written pieces of software.

      Well, since the systemd saga began, FreeBSD has been getting a lot more respect from a good section of the Linux crowd that hates systemd. OpenBSD gets it as well particularly from people w/ old RISC based Unixstations, since they are the only ones still maintaining those old platforms.

    14. Re: Really like FreeBSD by Bengie · · Score: 1

      Anyone who has worked on infrastructure projects will understand the necessity of a good design's importance to long term efficiency. Linus has made sure that the Linux kernel is a stable dependency on which to build your projects, but userland has no such thing. Everything is in constant flux. "Not invented here" is a rampant issue. Fix you current stuff before reinventing a slightly different wheel.

      New does not mean buggy unless you have piss poor programmers.

    15. Re:Really like FreeBSD by Bengie · · Score: 1

      You should try working on the Linux kernel. Linus has a much shorter fuse for idiots. Sometimes it's better to scare some people off than to let them poison the code with their ineptitude. FreeBSD is a meritocracy. Quality over political correctness.

    16. Re:Really like FreeBSD by rl117 · · Score: 1

      I did my first Linux installs in 1997 (slack/redhat), and first Debian install in early 2008. I used Debian as my primary OS from 2009-2015 initially as a user and after a few years as a fully-fledged developer. I started investigating options for moving away from Debian around the end of 2013-early 2014, and migrated all my local data to a FreeBSD NAS in Jan 2014. As I learned more about it, the more I liked it. While it's fair to say that systemd was the primary impetus for looking for a replacement, it was not the main reason for switching. ZFS was the killer feature for the NAS. clang++ was a later reason to start using it for development. Today, I have FreeBSD on my main desktop, and in multiple VMs in addition to the NAS system. Oh, and Debian kFreeBSD in a jail on the NAS along with a bunch of other dedicated jails for development, PostgreSQL, and other tasks. When it comes to having a UNIX system that I want to use and hack on, FreeBSD is now closer to my ideal than where RedHat and Debian have gone. In some ways it feels kind of like Debian did back in the late 90s/early 2000s, and I mean that in a good way.

      One of my workmates is also a long-time Debian user. A few weeks back, he got his first OpenBSD install and is also looking at his options for the future. His reasons: systemd and jessie, and he was very enthusiastic in how pleased he was with the OpenBSD install, and how he expected it to be more difficult to install and less featureful than he found it.

      I think what's really changed is our attitude to Linux. It got pushed into workplaces and adopted because of the grass-roots advocacy and effort of developers, sysadmins and users worldwide. We cared deeply about it and weren't just users, we were active participants in its development. With the corporatisation of Linux, particularly by RedHat, I find I really no longer care about it, and this is primarily because I am no longer directly engaged in its development after being completely disenfranchised by corporate interests. When it comes to supporting it for work it's now kind of like having to support Windows--it's a requirement of the job and it will be done, but it's nothing to be passionate about, just a necessary part of the job. And I think that indifference will be more harmful to Linux than anything else. Linux came more from volunteer effort than any corporate contribution, and I think that's been forgotten by the companies involved... to their detriment.

    17. Re: Really like FreeBSD by Anonymous Coward · · Score: 0

      BSDs...

      \s

    18. Re:Really like FreeBSD by DNS-and-BIND · · Score: 1

      Who's talking about the kernel? I'm talking about being an ordinary user. Where did I even say anything about programming, much less on the core of the system? Get your head out of your ass and stop assuming everyone else is like you.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    19. Re:Really like FreeBSD by Anonymous Coward · · Score: 0

      but when the FreeBSD solution exists it's a lot more pleasant to work with (compare kqueue vs epoll + timerfd + eventfd + ..., for example).

      How does that explain the atrocious rc.conf interface that tries to cram single daemon flags into half-sentence-variables, e.g. ntpd_sync_on_start instead of simply ntpd_flags="-g". Who needs this shit?

      Compare interface configuration on OpenBSD with FreeBSD. OpenBSD: completely simple, flexible and powerful /etc/hostname.$if files (granted, the naming is awkward and they tried to impose some custom keywords instead of having a completely transparent interface to ifconfig(8). NetBSD is even better in that regard). FreeBSD: man rc.conf and try to figure out how they tried to map a convolute of rc variables to simple ifconfig(8) usage - with gems like interface aliases needing to be defined in continuously named variables. If you skip a variable or comment it out temporarily, it just ignores all the rest. Tried to be "easier", made a whole mess out of it and now you have inflexible bullshit.

      Or try to netboot a FreeBSD _without_ having its runtime network configuration match the netboot configuration, i.e. you boot from a storage network while general connectivity is on a completely different network. Not possible, because genius bullshit like resolvconf(8) (yes, that's the name of a program, I shit you not and its configuration is... resolvconf.conf! Fucking hell!) forcefully graces you with the DNS config of the storage network with no actual way to override it, short of completely disabling it by "exit 0" in its config file. Or maybe there is some rc.conf variable for it. I didn't give a fuck really. There's so much crap in FreeBSD where they try to be smart and hide stuff from you, when all they do is layer the simple tools with crap after crap.

      FreeBSD has become the Linux among the BSDs. Convoluted and unnecessary shit is robbing you of flexibility and power, in order to please some generation of admins who know jack shit. FreeBSD forgot how to do "simple" and instead went in a direction of assumed "easier" while tripping over its own training wheels.

      If you want truly "simple", go OpenBSD. To build powerful systems, you need simple components, without unnecessary logic that tries to be "easier".

    20. Re:Really like FreeBSD by Anonymous Coward · · Score: 0

      If you want truly "simple", go OpenBSD. To build powerful systems, you need simple components, without unnecessary logic that tries to be "easier".

      OpenBSD: the BSD that still doesn't have Thread local storage in 2015.

      What a joke.

    21. Re:Really like FreeBSD by Bengie · · Score: 1

      I assumed you were talking about the developers because the community is great. Very nice and helpful people. Maybe you have a social issue and find any amount of push back to be threatening.

  6. Re:Ob by Anonymous Coward · · Score: 1

    No, and it never will, it's simply not the BSD way of doing things, nor is there any point, nor is it cobbled together by a bunch of randoms into "distros". BSD is single source and it just works, always has, always will. Linux people who have never actually USED a BSD simply don't understand the concept. That's unfortunate.
    But since BSD is opensource unix, you can always hack it to do whatever you want :)

  7. Painless upgrade by rl117 · · Score: 5, Informative

    Just finished upgrading all my work and home systems and VMs, plus one clean install. Smooth painless upgrades from 10.1-RELEASE and no problems encountered, all systems running nicely. Great work, team, your efforts are much appreciated.

    FreeBSD merrilin.codelibre.net 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64

    1. Re:Painless upgrade by Bengie · · Score: 3, Interesting

      FreeBSD foundation has a server that was originally FreeBSD 5.0 32bit and has been in-place upgraded all the way up to FreeBSD 9.3 64bit, not to mention migrated through several physical servers through the years. There are still original FreeBSD 5.0 binaries that are still running and to which they no longer have the original source code.

      Even when pushed beyond any sane limits, FreeBSD keeps on trucking.

    2. Re:Painless upgrade by Anonymous Coward · · Score: 0

      maximum cheering!

      Windows is death knell.

    3. Re:Painless upgrade by Eunuchswear · · Score: 1

      There are still original FreeBSD 5.0 binaries that are still running and to which they no longer have the original source code.

      No longer have the original source code? Who are these guys, Microsoft?

      --
      Watch this Heartland Institute video
    4. Re:Painless upgrade by unixisc · · Score: 1

      Somehow, I have no idea what version I have successfully upgraded to, given what I get: [lintel@cisc] ~% uname -a
      FreeBSD cisc 10.0-RELEASE-p19 FreeBSD 10.0-RELEASE-p19 #0: Thu Nov 6 21:53:58 UTC 2014 root@amd64-builder.pcbsd.org:/usr/obj/usr/src/sys /GENERIC amd64
      [lintel@cisc] ~%
      I'll just wait for PC-BSD 10.2 to become final so that the upgrade can finally go through. I've tried doing it the CLI way too, but hasn't been any different.

    5. Re:Painless upgrade by rl117 · · Score: 1

      When you say, "wait to become final", it is final now as far as I can tell. Can't you run:

      freebsd-update -r 10.2-RELEASE upgrade
      freebsd-update install
      reboot
      freebsd-update install
      pkg update
      pkg upgrade

      That's pretty much what I did for all the systems I upgraded to 10.2.

    6. Re:Painless upgrade by Anonymous Coward · · Score: 0

      unixisc here (logged on from a different login on an admin privileges account on the same laptop to do the above steps). I get the following errors when I try it:

      [bsd@cisc] /usr/home/bsd# freebsd-update -r 10.2-RELEASE upgrade

      Looking up fbsd-update.pcbsd.org mirrors... none found.

      Fetching metadata signature for 10.0-RELEASE from fbsd-update.pcbsd.org... done.

      Fetching metadata index... done.

      Fetching 1 metadata patches. done.

      Applying metadata patches... done.

      Fetching 1 metadata files... done.

      Inspecting system... done.

      The following components of FreeBSD seem to be installed:

      kernel/generic world/base world/doc world/games world/lib32

      The following components of FreeBSD do not seem to be installed:

      Does this look reasonable (y/n)? y

      Fetching metadata signature for 10.2-RELEASE from fbsd-update.pcbsd.org... done.

      Fetching metadata index... done.

      Fetching 1 metadata patches. done.

      Applying metadata patches... done.

      Fetching 1 metadata files... done.

      Inspecting system... done.

      cat: stdout: Broken pipe

      Fetching files from 10.0-RELEASE for merging... done.

      Preparing to download files... done.

      Fetching 3232
      patches.....10....20....30....40....50....60....70....80....90....100....110....120....130....140....150....160....170....180....190....200....210....220....230....240....250....260....270....280....290....300....310....320....330....340....350....360....370....380....390....400....410....420....430....440....450....460....470....480....490....500....510....520....530....540....550....560....570....580....590....600....610....620....630....640....650....660....670....680....690....700....710....720....730....740....750....760....770....780....790....800....810....820....830....840....850....860....870....880....890....900....910....920....930....940....950....960....970....980....990....1000....1010....1020....1030....1040....1050....1060....1070....1080....1090....1100....1110....1120....1130....1140....1150....1160....1170....1180....1190....1200....1210....1220....1230....1240....1250....1260....1270....1280....1290....1300....1310....1320....1330....1340....1350....1360....1370....1380....1390....1400....1410....1420....1430....1440....1450....1460....1470....1480....1490....1500....1510....1520....1530....1540....1550....1560....1570....1580....1590....1600....1610....1620....1630....1640....1650....1660....1670....1680....1690....1700....1710....1720....1730....1740....1750....1760....1770....1780....1790....1800....1810....1820....1830....1840....1850....1860....1870....1880....1890....1900....1910....1920....1930....1940....1950....1960....1970....1980....1990....2000....2010....2020....2030....2040....2050....2060....2070....2080....2090....2100....2110....2120....2130....2140....2150....2160....2170....2180....2190....2200....2210....2220....2230....2240....2250....2260....2270....2280....2290....2300....2310....2320....2330....2340....2350....2360....2370....2380....2390....2400....2410....2420....2430....2440....2450....2460....2470....2480....2490....2500....2510....2520....2530....2540....2550....2560....2570....2580....2590....2600....2610....2620....2630....2640....2650....2660....2670....2680....2690....2700....2710....2720....2730....2740....2750....2760....2770....2780....2790....2800....2810....2820....2830....2840....2850....2860....2870....2880....2890....2900....2910....2920....2930....2940....2950....2960....2970....2980....2990....3000....3010....3020....3030....3040....3050....3060....3070....3080....3090....3100....3110....3120....3130....3140....3150....3160....3170....3180....3190....3200....3210....3220....3230. done.

      Applying patches... done.

      Fetching 5830 files... 1dccdbd8071ed17939c5e9ed1c772853d7a1a02af423ba24

    7. Re:Painless upgrade by StarKruzr · · Score: 1

      Are you running VMs on FreeBSD? Is there a good management system for this? I'm running Proxmox VE at home and have been really happy with it; curious if you've had a better experience on BSD.

      --

      +++ATH0
    8. Re:Painless upgrade by rl117 · · Score: 1

      I'm afraid not. On FreeBSD itself, I only have jails at the moment. I did give VirtualBox a brief try, IIRC.

      I have FreeBSD guests on a work VMware ESX cluster, and on VirtualBox and VMware Workstation on my personal development machine (Linux and Windows). At home, I have the same (VirtualBox and VMware Workstation on Linux and Windows).

    9. Re:Painless upgrade by Anonymous Coward · · Score: 0

      You're the guy who was caught at WindowsIT Pro by apk lying you're not Jarrett DeAngelis: I remember that. You post at arstechnica as StarKruzr and there on that magazine's site too and it's where apk annihilated your ass and especially Jay Little and Jeremy Reimer too. Little said "I am an expert on exchange" and when apk proved that memory optimizer tech unhalted exchange servers you both got fried. Your lies really did you in those Jarrett. Bad move. You're a known online lying piece of shit.

  8. WTF Dice?!! by Thud457 · · Score: 3, Insightful

    This is a BSD story, why isn't it using the slashdot red BSD theme?!! Did Coyboy Neal take it when he left?

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    1. Re:WTF Dice?!! by KGIII · · Score: 4, Funny

      When he left? No. He came back drunk one night and stole it, however. They say he was wearing a cowboy hat, nothing else, and covered in spaghetti sauce. Some folks say it was blood. Nobody dared taste the drippings and nobody wanted to call the cops.

      --
      "So long and thanks for all the fish."
  9. Re:Fuck FreeBSD by Anonymous Coward · · Score: 0

    You are free to use and say whatever you want. Have a nice day.

  10. Re:Ob by Anonymous Coward · · Score: 0

    Chuck Norris can crash systemd with one fist
    Chuck Norris uses FreeBSD
    Windows 10 Assholes

  11. PC-BSD is pretty good, too by epine · · Score: 4, Insightful

    I had never run BSD on the desktop before, but recently I converted both my desktop and my aging T500 laptop to PC-BSD. The experience has been pretty good so far.

    I especially like the boot environment upgrade process. The only thing you need to be aware of is not installing new software on your system after the ZFS clone. Otherwise the upgrade process affects you not at all until you're good and ready to boot into it, and at that point if anything goes wrong, you just roll it back and wait for next time.

    Then I look at my real FreeBSD server and wish it was equally slick.

    My biggest problem with PC-BSD is that Life Preserver does something with SSH that's just never worked for me. I've tried multiple clients to multiple servers. I've emulated the SSH part of the connection process at the command line, no problem. But after setting up the same connection, Life Preserver bombs out with a generic (aka useless) error message.

    Mostly it just works, but when it doesn't I've found some of the error messages extremely unhelpful.

    (Yes, I know how to wrapper SSH to diagnose this properly, but I just haven't found the time yet.)

    1. Re:PC-BSD is pretty good, too by michaelmath · · Score: 4, Interesting

      I tried OpenBSD on a new Dell laptop. I thought I would end up writing over it, but I experimented and found that it is awesome. Everything I want is working: encrypted home partition, sound (hd-intel), 3d hardware accelerated graphics (intel card), suspend, wifi internet (with a tiny dongle), my wireless mouse, touchpad. all of my favorite applications are in ports and chromium is working fine. After all that I ended up keeping Openbsd as my desktop. It feels much cleaner, I like how everything is organized. Of course it can't use as many devices as linux. YMMV

    2. Re:PC-BSD is pretty good, too by Anonymous Coward · · Score: 0

      First of all I've actually never run into a system that wasn't fully supported by OpenBSD and yeah but you can sleep securely at night not having to worry about getting pwned in 5 minutes when you're on OpenBSD vs other OS. I fully support your choice and your experience mirrors mine.

    3. Re: PC-BSD is pretty good, too by Anonymous Coward · · Score: 1

      Yes, OpenBSD is the only viable candidate for laptops now. FreeBSD development has stalled. All of their big commits over the past decade have been back porting features from open source Solaris (ZFS, capsicum, dtrace). But graphics support for modern desktops (or laptops) has basically been: get an nVidia driver, or go home. No Intel support, nothing for radeon that isnt broken in some fubdamental way. No working suspend/resume from X. Why? Because all of the FreeBSD developers are running the operating system in a VM on their Macs. That has been the bane of FreeBSD development for the past decade.

      OpenBSD developers eat their own dog food. It is often he source of WiFi drivers used by other FOSS systems. Intel and radeon (up until the 6800/7600 series thanks to blobs) just work out of the box. Suspend/resume works, instantly. Even the WiFi card on my broadwell laptop works properly (although no hardware graphics acceleration yet thanks to Intel now requiring blob drivers). The latest GNOME works. The system is easy to configure, and has sane, simple config files.

    4. Re:PC-BSD is pretty good, too by TheRaven64 · · Score: 1

      I especially like the boot environment upgrade process. The only thing you need to be aware of is not installing new software on your system after the ZFS clone. Otherwise the upgrade process affects you not at all until you're good and ready to boot into it, and at that point if anything goes wrong, you just roll it back and wait for next time.

      We currently have a GSoC student working on improving BE support in the ZFS loader. For 11.0, we'll planning on using pkg for the base system (which should make it possible to move between -RELEASE, -STABLE and -CURRENT branches a bit more easily and mean that -STABLE gets wider testing - we've benefitted quite a bit from PC-BSD shipping some experimental stuff). Nexenta has a nice model for apt-clone that inspired the PC-BSD stuff - we'll likely use something similar, so pkg will do a snapshot and then the upgrade, making it trivial to roll back.

      --
      I am TheRaven on Soylent News
    5. Re:PC-BSD is pretty good, too by Anonymous Coward · · Score: 0

      Talking about the boot upgrade process, is there an UEFI enabled option in FreeBSD/PC-BSD? After I upgraded my system, I found that having UEFI enabled was not an option if I wanted my system to actually boot

    6. Re:PC-BSD is pretty good, too by phoenix_rizzen · · Score: 1

      Install the beadm port and you get the same boot environment setup. It was actually available on FreeBSD first. PC-BSD just included it in their installer image.

  12. Re:Ob by Anonymous Coward · · Score: 1

    Chuck Norris is nothing...
    Linux can crash systemd with one fstab missing a mount

  13. Re:Ob by Anonymous Coward · · Score: 2, Informative

    I know parent was marked Funny, but uselessd is a very real thing: http://uselessd.darknedgy.net/

  14. Re:Not threatened by garbage by Anonymous Coward · · Score: 0

    Linus doesn't consider the kernel to be "hijacked".

  15. Re:Ob by mrchaotica · · Score: 1

    Haiku version:

    systemd crashes
    under Chuck Norris' one fist
    Windows 10 assholes

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  16. Re:FreeBSD is for cows. by Anonymous Coward · · Score: 0

    Seriously sexconkers or whoever sexconker imitator you are, don't you get tired of that joke?

  17. Re:Ob by Anonymous Coward · · Score: 0

    What is BSD? Does BSD have a single repository somewhere or is it just a name that doesn't mean anything anymore? Can't we just talk about it as FreeBSD, OpenBSD etc. as separate entities? Because they are. There is no such thing called BSD anymore.

  18. NAS4FREE by Anonymous Coward · · Score: 0

    I use NAS4Free which is FreeBSD on a USB stick designed for running NAS servers. One of the big pains is the out of date ZFS support. Solaris had done more work on ZFS but it wasn't open sourced, ZFS encryption specifically.

  19. Re:Ob by phantomfive · · Score: 1
    From the Uselessd website:

    uselessd is dead. The last release was uselessd-8 on November 16, 2014. An effort to revamp the IPC system away from D-Bus into using a byte stream-based fifodir protocol was staged for uselessd-9, but a growing lack of interest and realization that trying to mangle the systemd architecture into something more minimal was becoming increasingly fruitless and unwieldy lead to the project being orphaned. It was transferred to Tarnyko in January 2015, but no activity of any sort has been seen since then. For all practical purposes, it's over.

    --
    "First they came for the slanderers and i said nothing."
  20. FreeBSD on the Desktop. by srobert · · Score: 5, Informative

    A lot of people say FreeBSD is best on the server, while Linux is best on the desktop. But I was a long time Linux user and started playing around with FreeBSD a few years ago. It turns out, that IF your hardware is compatible with it, and IF you know what you're doing, then FreeBSD is also best on the desktop.

    1. Re:FreeBSD on the Desktop. by cbhacking · · Score: 1

      Not that I disagree, exactly, but can you give some reasons why? I've tried running BSD desktops - both pure FreeBSD and desktop-oriented distros like DesktopBSD and PC-BSD - and while its certainly viable I don't know that I'd call it superior. ZFS is pretty awesome (though getting it set up correctly was a bit of a trick) but not sufficiently better than the current crop of Linux FS options to sway me that much. What else have you found that's better on BSD? Actual examples, please.

      I'll be rebuilding my desktop soon, and while a Windows partition is sadly a given, I will also have at least one Linux and/or BSD install. I'd like to know which one(s) I should use, according to the current wisdom, and why.

      --
      There's no place I could be, since I've found Serenity...
    2. Re:FreeBSD on the Desktop. by walterbyrd · · Score: 0

      I think Red Hat has been working to monopolize Linux. I think it's been going on for years. Systemd was a huge step towards such monopolization.

      Red Hat wants to be Microsoft. Who could blame them? Red Hat is imitating Microsoft in many ways. Systemd is open just like OOXML is open. Red Hat is using it's dominate position to push technologies on people who don't want those technologies.

      Pottering has made no secret of being a huge fan of the Microsoft way of doing things, and a hater of the traditional UNIX/Linux way of doing things.

        It seems to me that, if you are a fan of the way that Linux is going, you would be happier with MS-Windows, or maybe OSX.

    3. Re:FreeBSD on the Desktop. by kyubre · · Score: 2

      In short, FreeBSD/PC-BSD is to the Linux desktop user experience what RHEL is to Linux in general

      I've been running PC-BSD as my primary desktop OS for about 5 years now. I say desktop, but I mostly use some variation of T-Series thinkpad as "my desktop". In the for what its worth, I also have several server class machines running RHEL compatible, Arch, and of course plain FreeBSD (which PC-BSD is mostly a specialization of).

      I also find PC-BSD/FreeBSD to be the best desktop experience but with caveats.

      To those familiar with the Linux ecosystems, Comparing the FreeBSD/PC-BSD Desktop to Linux is almost exactly like comparing Redhat to Arch Linux (perhaps the Ubuntu's as well). Distro's like Arch tend to have the latest greatest of everything, and everything "mostly" works. You can tweak and fiddle with it to your hearts content, and their is no "standard" configuration. A RHEL distro by contrast, is chosen for its consistency and POLA features (Principles of Least Astonishment). There is a clear definition of how everything on a RHEL distro is supposed to work and it will be maintained to those standards.

      FreeBSD/PC-BSD is very similar. There are very clear definitions of the entire stack from userland to kernel with each major release. It is very actively supported to those definitions and expectations, as well as fairly strict adherence to POSIX definitions where available.

      The user land apps may not be the latest greatest, but they are generally stable (I hate that Thunderbird is still stuck at v31!). The one noticeable exception is web browsers and their flash support. Both FireFox and Chromium seem to leak resources when running Flash heavy web sites and I must routinely pkill them after several of hours of heavy use (dozens of active tabs open for hours). Thankfully, Flash is dying a long over due death of its own making.

      With the exception of browsers and flash support mentioned, everything else just works and tends to be rock solid with very few POLA violations even between major version numbered updates. Add to that the most excellent ZFS support on PC-BSD (and associated incremental snapshoting/backup options it enables), I can say that I have never once lost a byte of data unintentionally through every update and release since FreeBSD 8.2. I've also not suffered a single crash ever that was not due to an out of memory condition caused by Chromium and its messed up Flash NaCL/PNaCL support.

      --
      Nothing evolves faster than the word of god in the minds of men who think themselves divinely inspired.
    4. Re: FreeBSD on the Desktop. by Anonymous Coward · · Score: 1

      Oh, come on. RedHat *is* Linux, and has been for close to twenty years. No other single entity has come close to the number of committed lines in the kernel over the years, or the development of user land and user-facing tools. GTK+ and Gnome are de-facto RedHat projects, as are many things we take for granted in a modern distribution (pulse, systemd, gstreamer). RedHat hasn't monopolized anything that wasn't already theirs; maybe only Google comes close to leadership in the Linux world, and they are far worse when it comes to straying from traditional UNIX.

      And unlike Google or Apple, all of RedHats contributions have been FOSS. They became a billion dollar company by selling support, while giving their code away for FREE, and not infringing on end-user rights (as a matter of fact, their community distribution refuses patented codecs out of the box, which makes it somewhat painful, but shows RedHat actually standing true of its values).

      I am an OpenBSD die-hard now, after having used FreeBSD exclusively at home for 15 years, and I have a great deal of respect for what RedHat has done over the years. Quit the RedHat bashing, please. We are all better off because of RedHat, and the FOSS world would really be a worse place without their influence.

    5. Re:FreeBSD on the Desktop. by srobert · · Score: 2

      Consistency. When you learn to do something in FreeBSD, chances are that what you learned will remain relevant for a long time. Some Linux distros seem to impose change for it's own sake.
      I like the simplicity of many OS related configurations being done through only a few (plain text) files such as rc.conf and sysctl.conf.
      There is a clear separation of the base of the FreeBSD operating system from the end user applications, which is reflected in the file system layout. For example OS related configuration files (in plain text) are in /etc, while end user software configuration is reliably in /usr/local/etc. This makes it very easy to administer software updates. If things do get broken, (as they do with all OSes), it's easy to locate what went where.
      The documentation, such as the FreeBSD Handbook, is very good, complete and comprehensible to me, whereas help for Linux related problems is becoming more fragmented. "If Slackware, do this, if Debian do that, for Arch, do something else".
      I tend to like to do these things from the bottom up. When I was in Linux, I built Linux from Scratch several times. Every application that was installed from source had a unique and complex build command described in the LFS book. With FreeBSD, the command is pretty much the same for all the software in the ports tree to build it from source, e.g. "cd /usr/ports/www/firefox" then "make install", or "cd /usr/ports/shells/bash" then "make install". There are tools like portmaster to make it even simpler than that.
      PC-BSD and GhostBSD are pretty good. DesktopBSD is now obsolete I think. But I prefer to work from the bottom up, so one good resource to approach it this way is https://cooltrainer.org/a-free...

    6. Re:FreeBSD on the Desktop. by dbIII · · Score: 1

      Not that I disagree, exactly, but can you give some reasons why?

      Faster on old hardware while still giving you firefox, thunderbird etc.
      If you have enough drives to feed ZFS a mirror or two, a lot faster.
      That's really the reason, a lot less is going on so it is quicker. If you have a lot of fast cores and enough memory then the speed increase is not going to be noticed - apart from disk access, so the advantage is less clear since the applications are often going to be the same anyway (athough sometimes linux is noticably slower due to distro defaults that you can change there as well).

      Another reason, which will not appeal to all but is a benefit to some, is that you can use the ports collection and compile your applications to match your hardware. This can be a big deal since binaries are built typically for the lowest common denominator and your CPU is likely to have a lot of instructions to speed things up that the AMD hammer didn't have a decade plus ago. Gentoo linux also does that but the ports collection is a lot easier to use. It consumes a bit more time than the binary upgrade methods on FreeBSD and linux but makes a noticable difference with both recent 64 bit and late model 32 bit systems. You can also turn on or off building various parts of applications via a simple menu before compiling. Thus netbooks with little memory and not a lot of speed, with a 32 bit CPU, become usable platforms for current window managers, current firefox, chrome, thunderbird etc. Even libreoffice can work on slow machines so long as you don't try to put a lot of images in documents or have massive spreadsheets.

    7. Re: FreeBSD on the Desktop. by oddtodd · · Score: 2

      Spot on, I tried to tell walter this in a different forum and it didn't register, apparently.
      Hi Walter! Funny Cin U here

      --
      I have plenty of common sense, I just choose to ignore it. -- Calvin
    8. Re:FreeBSD on the Desktop. by unixisc · · Score: 1

      FreeBSD for the desktop is PC-BSD. Or, if you are referring to a CLI only experience, then FreeBSD on the desktop is TrueOS

    9. Re: FreeBSD on the Desktop. by rl117 · · Score: 1

      RedHat has certainly made a lot of valuable contributions, particularly to the kernel and toolchain.

      Their influence on GNOME and GTK+ is a bit more debateable. Do you remember what they were like in the 0.9/1.x days? They had participation from a wide range of companies and volunteers, and even if it was riddled with bugs it had the prospect of being something pretty amazing. Today, many of the original design flaws remain and many have had a lot of polishing, but the vibrant atmosphere and sense of progress have been lost. What it's lost is difficult to define precisely, but I think a large part of it is that it's lost perspective--when a project has a lot of people with different ideas all pulling it in different directions, it leads to a more rounded result whereas with only limited ideas, it ends up being insular on an inward-spiralling trajectory.

      I don't think that the long-term health of these projects is good, and I think RedHat's management of the developers it put into place on these projects has not been ideal. While it serves their purpose to have control over the direction of these projects, it stifles any long-term viability when any non-RedHat-aligned suggestions or contributions are rejected. And with RedHat taking over an increasingly large number of basic Linux packages, and of course systemd, it leads to stagnation. And it's contrary to what made Linux great in the first place, and not just another commercial Unix.

    10. Re: FreeBSD on the Desktop. by Anonymous Coward · · Score: 0

      Sure, I remember those days. But I was still a kid on a 486, so GNOME was too slow for me, and I got by with blackbox and KDE apps. But I remember the excitement around Linux at the time. Everybody was getting into it -- Corel, IBM, Sun. It was fueling startups left and right, Eazel comes to mind wrt GNOME, there are more I'm forgetting. But that was three recessions ago. Those companies are long gone. RedHat stands alone as the sole player in that field, and did it without closing the source, or backdooring their shit for the NSA. Remember that in those days, Apple was a non-player, and Google was just a startup search engine. These days, developers are excited about the mobile field. There is just less interest in general. Also, a good portion of people who would have experimented with Linux are on Macs now, which took away a good portion of users who wanted a desktop Unix. Its not RedHat's fault that they were the last major player left standing.

    11. Re:FreeBSD on the Desktop. by kafka0 · · Score: 1

      I've been using FreeBSD (plus NetBSD and OpenBSD before that) for quite some time on my personal servers as well as on my desktop and I must say I entirely agree with this: FreeBSD isn't just a server OS, it also really shines on the desktop. It's very easy to set up and keep up to date, the ports/packages system is rock solid, hardware support is very good... I also find running FreeBSD less demanding than Linux, Windows or OSX, with a lot less peculiarities to keep in mind. Also, hard-won knowledge doesn't get obsoleted as quickly as with other systems.

  21. Re: Fuck FreeBSD by Anonymous Coward · · Score: 0

    Amen! I need to preserve my safe space. But i went OpenBSD. Theo stood up to uncle sam. I dont see Debby or Ian doing so.

  22. Re: Fuck FreeBSD by Anonymous Coward · · Score: 0

    But bent over to take it from Microsoft. His infatuation with stack protection makes him blind to the privacy concerns and disregard for FOSS that Microsoft has shown. I doubt MS will be making a contribution to the foundation next year, and I'll bet that their OpenSSH implementation falls into an embrace, extend, extinguish cycle within ten years.

  23. Origin of BSD by PincushionMan · · Score: 1

    As I recall, BSD refers to BSD44 (or BSD v4.4), which I believe is the first version of Berkley Software Distribution [Unix] that was certified did not contain any of the SysV Unix code. Code that the university had obtained from Bell Labs for originally for training purposes. As I recall, there was a huge court battle over this in the 90s. Various pundits claim that if BSD had not been tied up in courts, hackers would not have taken an interest in the Minix clone, Linux. Then again, Linux had quite the court battle in the 2000s, and I don't remember FreeBSD users jumping through the roof. It takes quite a bit of dedication (e.g. time and desire) to track FreeBSDs -STABLE or -CURRENT. Was quite a bit of fun to compile your own kernel, though. Only one simple text file to read/modify.

    As I understand, you can obtain the BSD44 sources if you desire. They are not free, though. You have to pay for shipping and the cost of a 9mm reel or two. So yes, the BSD is important as it shows that all the *BSD distros come from a Sys-V Unix parent.

    1. Re:Origin of BSD by hansot · · Score: 1

      As I recall, BSD refers to BSD44 (or BSD v4.4), which I believe is the first version of Berkley Software Distribution [Unix] that was certified did not contain any of the SysV Unix code. Code that the university had obtained from Bell Labs for originally for training purposes. As I recall, there was a huge court battle over this in the 90s. Various pundits claim that if BSD had not been tied up in courts, hackers would not have taken an interest in the Minix clone, Linux. Then again, Linux had quite the court battle in the 2000s, and I don't remember FreeBSD users jumping through the roof. It takes quite a bit of dedication (e.g. time and desire) to track FreeBSDs -STABLE or -CURRENT. Was quite a bit of fun to compile your own kernel, though. Only one simple text file to read/modify.

      As I understand, you can obtain the BSD44 sources if you desire. They are not free, though. You have to pay for shipping and the cost of a 9mm reel or two. So yes, the BSD is important as it shows that all the *BSD distros come from a Sys-V Unix parent.

      As far as I know, BSD was not derived from System V but from V7 (via 32V). Early System V releases were based on V7 combined with a few internal Bell Labs systems.

      You can get the 4.4BSD-Lite releases as tar.gz file from all over the Internet (use Google to find one) or you could order the BSD archive CD-ROM set from Kirk McKusick (www.mckusick.com). I have not seen a tape distribution offered recently.

    2. Re:Origin of BSD by unixisc · · Score: 1

      Ok, it's not Free-as-in-beer, but is it Free-as-in-speech? In other words, is it licensed under any of the BSD licenses out there?

      I agree w/ the GP - we might as well talk about FreeBSD. Most of the BSD 'distros' out there - DragonFly, Midnight, Ghost, pFsense, et al are based on FreeBSD. Only thing based on NetBSD that I know of is OpenBSD, which has diverged quite a bit since it split. And OpenBSD just has one distro based on itself - I forget the name - the one that was made in order to be made from LLVM/Clang

    3. Re:Origin of BSD by Anonymous Coward · · Score: 0

      hackers would not have taken an interest in the Minix clone, Linux.

      You see, this is why nobody can really take BSD or it's proponents seriously: "OSX is BSD!" "Linux is a Minix clone!" "BSD users are clowns!" I'm tempted to add.

      No, OSX isn't BSD, and Linux is decidedly not a Minix clone, something anyone with even a passing interest in operating systems should know, since one is a monolithic kernel, and the other is a micro kernel based architecture. But hey, BSD-fans are as pathetically clueless as ever. The only connection that exists between Linux and Minix that exists, is that Linus used Minix to write the initial part of Linux. But that doesn't make Linux a clone of Minix any more than a letter you write in Word a clone of Word.

    4. Re:Origin of BSD by unixisc · · Score: 1

      Also, the Minix that Linus originally used, and the Minix of today are completely different - as different as Windows 3.1 and Windows 10. The original Minix 1 was not a microkernel, but today's OS is. You are right that Linux is not a Minix clone, but not for the reason you mention. Also, for the OS-X is BSD crowd, there is an equivalent Android is Linux crowd as well.

    5. Re:Origin of BSD by unixisc · · Score: 1

      The above refers to BSD, but is there any version of BSD that's based on this, as opposed to one of the big 3 - FreeBSD, OpenBSD and NetBSD?

    6. Re:Origin of BSD by hansot · · Score: 1

      The above refers to BSD, but is there any version of BSD that's based on this, as opposed to one of the big 3 - FreeBSD, OpenBSD and NetBSD?

      The big three -are- all based on 4.4BSD-Lite. OpenBSD forked off NetBSD around 1995. FreeBSD and NetBSD were originally (circa 1993) patched versions of 386BSD, which was based on the Net/2 release, itself intended as an unencumbered version of 4.3BSD. FreeBSD and NetBSD had to re-base their source trees to 4.4BSD-Lite when - as a result of the settlement of the lawsuit in early 1994 - Net/2 was considered tainted. As I recall FreeBSD 2.0 was the first version based on 4.4BSD. Of course the source code of the different projects has changed (and diverted) a lot since then.

    7. Re:Origin of BSD by Anonymous Coward · · Score: 0

      I have no insight in the earliest dawn of Minix, but it used message passing as far back as at least the late 80's, which strongly suggests Minix being a micro-kernel design predates Linux itself, and thus making the carefully implied claim that Linus used a monolithic version of Minix a bit questionable.

      None of that changes anything though; the micro/monolith example was just the simplest and most obvious example of why it's impossible to call Linux a "clone" of Minix and that the OP is either ignorant or an idiot. Better stem the tide here, we've already had idiots popping up, paid by Microsoft, saying that the "original Linux was an illegal copy of Minix". We don't need more of that kind of crap. Linus used Minix to write the initial version of Linux, just like the OP probably use Outlook to write his emails, but that makes Linux about as much a "clone" of Minix as it makes OP's emails clone of Outlook. End of story.

    8. Re:Origin of BSD by unixisc · · Score: 1

      I know that. However, since then, every distro of BSD has been based either on FreeBSD or NetBSD. Has there been any that wasn't based on either of these, but instead, based on 4.4 itself?

    9. Re:Origin of BSD by unixisc · · Score: 1

      What I meant was any other distro that's independently built from the sources of 4.4, and NOT from FreeBSD or NetBSD.

    10. Re:Origin of BSD by Anonymous Coward · · Score: 0

      NextStep and SunOS maybe, but that's about it...

    11. Re:Origin of BSD by Anonymous Coward · · Score: 0

      > No, OSX isn't BSD

      OS X is a BSD variant as much as any other. "Variant" meaning it originated with BSD code but changed, if you can grasp the concept of OS evolution.

  24. Re:Ob by unixisc · · Score: 1

    Uh, both GNOME3 and GNOME3 Classic Shell are already supported on FreeBSD 10.1. I have it on this PC-BSD laptop that I'm typing on right now

  25. SteamOS jails by unixisc · · Score: 1

    One thing that I do wish FreeBSD does is add a jail for SteamOS. I currently use a PC-BSD laptop, and to run Steam, it's recommended going into Wine. I'd prefer a solution where I can open a SteamOS jail and play my Steam games. It shouldn't be difficult, since support for Debian jails already exists.

  26. How is FreeBSD as a VMware/KVM guest? by billstewart · · Score: 1

    As far as I can tell from the documentation, FreeBSD isn't usable for as a production hypervisor unless you're willing to make a large investment in supporting bhyve (I don't count VirtualBox as production - it's fine for development, but too slow for production.) But how is it as a client on top of KVM or VMware? Can you run a usable system without burning too much disk or memory, compared to Red Hat or Ubuntu?

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:How is FreeBSD as a VMware/KVM guest? by StarKruzr · · Score: 1

      It's really bad as a guest on Linux. Unusably slow.

      --

      +++ATH0
    2. Re:How is FreeBSD as a VMware/KVM guest? by Anonymous Coward · · Score: 0

      You're the guy who was caught at WindowsIT Pro by apk lying you're not Jarrett DeAngelis: I remember that. You post at arstechnica as StarKruzr and there on that magazine's site too and it's where apk annihilated your ass and especially Jay Little and Jeremy Reimer too. Little said "I am an expert on exchange" and when apk proved that memory optimizer tech unhalted exchange servers you all got fried by him. Your lies really did you in those Jarrett. Bad move. You're a known online lying piece of shit.

  27. BSDs and RPIs by netgeezer · · Score: 1

    Both FreeBSD and NetBSD have been trying to get ARM releases
    out for a while. Neither is ready for Prime Time, but they're
    getting closer.

    I wish FreeBSD had gotten the armv7 architecture stuff into
    this release as a supported arch.

    I do have some early RPi boards, but also have (for anything
    serious) some RPi 2 B + whatever boards. And without the
    new boot code, they are useless for FBSD. Should be in the
    release, even with whatever warnings and caveats are needed.

    NetBSD has a not-really-release that supports the multi-core
    Pis.