Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
BSD Operating Systems

FreeBSD For The iMac And Other Eye-Openers 45

Anonymous Coward writes: "In this interview, part III, over at GNULinux.com you can read what Jordan Hubbard, CEO of FreeBSD Inc., has to say about the future of FreeBSD. '[...] Finally, the notion of the PC is changing. One could even argue that the PC has widened to encompass the PowerPC, because there are all these iMacs on peoples' desks, and according to the original mandate we should be looking at those iMacs, too, which is what we're doing,' sounds pretty sweet." This article provides a positive (but sober) overview of recent and anticipated progress from the devil-suit side of free software. You might also be interested in Jordan's answer to the question, "Can FreeBSD scale to the PDA?"
This discussion has been archived. No new comments can be posted.

FreeBSD For The iMac And Other Eye-Openers

Comments Filter:
  • Once again, you have it backwards. Solaris is the result of a merger between SunOS and SVR4. SunOS is based on 4.1BSD and 4.2BSD which predate Solaris by 5-10 years.
  • The same thing applies to the business world. Mac OS and FreeBSD (or Linux or whatever) complement each other quite nicely. Mac OS for usability, *nix for raw power.

    --
  • by seebs ( 15766 ) on Monday May 22, 2000 @07:12AM (#1057239) Homepage
    The main obstacles are technical and political; the NetBSD people have insisted on a few substantial differences in kernel structures. Still, code has been shared in the past, and probably will be in the future.

    Anyway, where do you think the Alpha port came from? Lots and lots of code was "borrowed". (In fact, this is one of the old grudges; some of the people who did the BSD-on-Alpha work originally feel they didn't get fairly credited for their work when it got borrowed.)

    Anyway, the code is out there, and anyone can use it. Neat, huh? It's sort of like *actually* free software.
  • >ead alan cox's papers

    Got any proof to back this up? The rest of your rant is without merit, so I'd be happy to see a URL where Mr. Cox makes claims of 'stealing'.

    (I guess if you are trolling and mention alan cox, you don't get flamebait, but get a +1)

  • Since I started running things like Linux and FreeBSD, in the height of the PC/Mac wars, suddenly I was no longer taking sides.

    Indeed, I don't care anymore what my hardware is. Even a 486 or a Sparcstation 1 is something I can use. Macs and PC's look pretty much the same to me unless I want to add some hardware to them, which I am comfortable with either way.

    This is a really positive thing. Once the software runs on everything, the hardware will come to the aid of the software and I think things might become a bit more uniform.

    Well, that's just wishful thinking. We aren't nearly as much a slave to the hardware manufacturers anymore, though, are we. "No, that costs too much for what it's worth. I will jump to architecture X instead. No skin off my nose."

    --Gabriel
  • PC stood for Personal Computer in the generic sense right up until the moment IBM released a PC brand named "PC"... then it became a brand name. Of course that brand name fell victim to the "Kleenex" syndrome in ensuing years.

    The mac is not a PC

  • NetBSD/macppc [netbsd.org] already runs on the iMac [apple.com]. We've been there for over a year (since the 1.4 release in May 1999).

  • The PPC is known to be one of the worst targets, right up there with Alpha.

    With IBMs commitment to Linux on the RS/6000 series I'd assume that they are going to be throwing some weight behind a gcc optimization for PPC. If they come out with an updated RS/6000 Thinkpad, I'm there, baby, I'm soooo there...
  • by Anonymous Coward
    No, people use *MacOS* to avoid such scenarios. People might want to run FreeBSD on their Macs simply because they like the hardware more than the PC equivalent. You seem to imply that current Mac users would never want to run FreeBSD on their machines, which is perhaps true for the vast majority of them. I'm saying that current FreeBSD users might want to run FreeBSD on a Mac, which is something else entirely. Besides, Linux on the Mac has met with some modest success, it would only be natural to port FreeBSD as well.
  • Do note that BSD/OS has a StrongARM port (IIRC), which will be merged into FreeBSD, so it's not as far off as you may think.
  • by phandel ( 178702 ) on Monday May 22, 2000 @04:43AM (#1057248) Journal
    Since the iMac now apparently has enough people using it to warrant a FreeBSD port, does this mean {the FreeBSD team, someone else} will help work on gcc optimization? The PPC is known to be one of the worst targets, right up there with Alpha.
  • Uhm, you've got it all backwards, buddy.

    Linux stole BSD code (PPP Compression code? How many networking and other utilities?). Linux imitates BSD (BSD has been around since before I was born, I remember when Linux was new).

    As for security, stability, and scalability, why don't Hotmail or Yahoo! use Linux? It's simple, Linux just cannot handle it. Dave Filo even said they tried Linux for Yahoo! and it just couldn't handle it.
  • We are using an iMac with Linux at my work, and let me say... seeing a command prompt on it brings a tear of joy to my eye. =^)

    Seriously, though, it is a Good Thing to have all of these *nixes going to the Apple arcitecture. Changing the OS on my (company issued) iBook from MacOS to Linux has given me a whole new respect for the hardware. Under Linux, the G3 is fast. The iBook in peticular is quite sturdy and cheap. I would actually consider buying one now that I have used *nix on it. I can't wait to try FreeBSD on it when it comes out.

    What I would like to see next is cross-platform Airport support under *nix... that thing is pretty schwank under MacOS.
    Just how i see it.
    -legolas

    Which is worse: Ignorance or Apathy?

  • Erm, yeah .. Kernel 2.0.x did suck but i'm quite sure 2.2.x or 2.3.x (2.4) could handle it.
  • Unless there is an MMU available, you can't run FreeBSD on it-- which excludes most PDAs right off the bat.

    Is there a uFreeBSD project like uLinux? Maybe there should be...

  • by Anonymous Coward
    Wrong once again. SunOS/Solaris is based on Windows NT 3.5. They made it look nice and pretty but it's the same underneath. I have sources in Microsoft that showed me secret documents that Sun signed for the code.
  • Baloney. FreeBSD can't run on any PDA that doesn't have an MMU

    So? I didn't say anything about PDAs. There are a lot of other applications besides those. For instance, the industrial security project I should be working on right now...

  • The real question is if the general public will accept the Macintosh into the Linux/BSD community. Without question, Apple makes a fine computer, but many users, especially system admins, refuse to admit that anything but Dell, Compaq, or other namebrand Intel/AMD base should be used for their servers. At some point, this becomes a war of religion, not OS. Jihad!
  • by slim ( 1652 ) <john@@@hartnup...net> on Monday May 22, 2000 @06:04AM (#1057256) Homepage
    I freely admit to not knowing as much about the BSD license as I do about the GPL: how much trouble, both technically and legally, would it be to merge the platform specific code from the various NetBSD ports into the FreeBSD tree?

    (and would there be any point)

    On a side note -- I presume "Gift-F" was the interviewer mishearing "#ifdef", right? So neither the author nor the editor bothered to understand their own sentence...
    --
  • Who cares? They all stole from Bell Labs and AT&T anyway...
  • by Arandir ( 19206 ) on Monday May 22, 2000 @09:25AM (#1057258) Homepage Journal
    Technically, I don't know. Legally, absolutely no problem whatsoever. Go read the BSD license. It'w quick, easy, understandable, and small enough to actually include in the header of each and every one of your source files.

    The BSD community sometimes refers to licenses as "encumbered" or "unencumbered". Unencumbered means that the developer doesn't have to propogate someone else's restrictions onto his own code. Anything beyond "do whatever you want as long as you pass on this permission and warranty statement" enters the realm of encumbering.

    The BSD community takes the opposite tack of the GPL community, focusing on the 99 people who will do the right thing, as opposed to the one person who won't. To rephrase the biblical lesson, the two cents given by the widow hacker freely and without regret far outweigh the millions given by the pharisaic developer who did it just because the license said so.
  • If they want to be portable to, say, IA64, then they have to use a high-level language. If they have it in a high-level language, why not compile to other platforms as well? Getting PPCBSD out doesn't mean they're not still optimizing for x86's, and they're definitely reaching more people, as well as reducing Intel's (and x86's) hegemony over the processor world.

    Ramble on!
    mfspr r3, pc / lvxl v0, 0, r3 / li r0, 16 / stvxl v0, r3, r0
  • Not that folks can't figure it out for themselves, but the Mac PowerPC port is at http://www.netbsd.org/Ports/macppc" [netbsd.org].

    Jordan Hubbard is welcome to look at the iMac, but it sure seems like reinventing the wheel, since NetBSD/macppc works just fine as far as I can tell:

    uriel:~% uname -mprs NetBSD 1.4R macppc powerpc uriel:~% uptime 5:50PM up 11 days, 33 mins, 4 users, load averages: 0.19, 0.10, 0.09 ... and that's just because I have no UPS during power outtages.

    (It's a PowerMac 7500 with a G3 processor card.)
  • ... except that MacOS X descends from NeXTStep, which is different (kernally) from modern BSD in a lot of (both bad and not so bad) ways.

    That said, Darwin's fairly up to date, but it's not the same code (or, most likely, the same design ethic) as BSD.

    Even more, MacOS X uses the Mach Microkernel (as MkLinux does and LinuxPPC does not), which makes it very different from NetBSD/macppc (which, as plenty of people have noted, already exists and already runs on iMacs just fine, thank you), which boots through the Mac's OpenFirmware (hold down command-option-O-F on a PCI-arch mac).
  • this step should have been obvious, what with osx using elements of the BSD kernel already.
    -----BEGIN GEEK CODE BLOCK-----
    v.3.12
    GCS d-(--) s+: a-- C+++$>++++$$ UL++$>++++$$ P+>++++$ L++>++++$ E--- W++$>++
  • by SecretAsianMan ( 45389 ) on Monday May 22, 2000 @04:01AM (#1057263) Homepage

    Lots of work by many experienced gurus has already gone into adapting FreeBSD for small applications. Currently, there is a development kit known as PicoBSD that enables one to automatically build floppy images that contain a minimal FreeBSD. Other people have created their own custom embedded versions of FreeBSD; the tight integration and cleanness of FreeBSD and its source tree make it quite easy for even an amateur to roll his/her own version. I myself am currently working on an improved development kit for building embeddded versions of FreeBSD quickly and easily. It's output is currently running off of an 8MB DiskOnChip on the desk to my right.

    For more information, see Small FreeBSD Home Page [freebsd.org]. It's a bit outdated, but work is still actively going on. A maintainer is currently working on improving the site. To get at the very heart of things, subscribe to the freebsd-small mailing list (info here [freebsd.org]) or read the archive [freebsd.org].

  • by matticus ( 93537 ) on Monday May 22, 2000 @03:27AM (#1057264) Homepage
    from what i understand of FreeBSD, their point is to make the best possible BSD for the x86. I believe they have a port to the Alpha, but when i talked to them at Comdex, i was under the impression that was sort of an experimental thing they did for fun-they are focusing on improving x86 FreeBSD and leaving everything else to their bsd brethren. is this symbolic of a new direction in FreeBSD? or have they received enough support to begin to develop for the PowerPC? or is this just a fluke? I'm all for them staying in the PC market-FreeBSD is as solid of a server OS as you'll find anywhere. but...i'm not them.

    "the problem may have been that there was a stonehenge monument on the stage that was in danger of being crushed by a dwarf!" - David St. Hubbins, Spinal Tap

  • I'd rather like to have BSD running on my Mobile Phone .... ;) gsmBSD .... ....
  • No no, the iOpener is a different cute, cheap box. ;)
  • Chuck on the iMac with all the ports =)
  • Interesting to read the bit about how FreeBSD linked up with Walnut Creek CDROM. Is it possible that without Walnut Creeks kind response, FreeBSD as we know it would either not exist, be later coming along???

    "A goldfish was his muse, eternally amused"
  • Why not just use Darwin?

    I finally managed to get it d/l'd, it installed easily enough, now I just need to setup CVS accesss through our Proxy here at work and hopefully I'll be all set.

    Wiliam

  • by tpv ( 155309 ) on Monday May 22, 2000 @04:07AM (#1057270) Homepage
    their point is to make the best possible BSD for the x86
    You could more say their point was to make the best BSD for the x86, but even that's no quite true.
    386BSD came out, and the FreeBSD guys (who obviously weren't FreeBSD guys then) thought "Cool, UNIX for the masses. And it's free. We like this." But 386BSD never went anywhere. It jumped out of the blocks, but then stopped, and so FreeBSD started where 386BSD left off.

    Their goal was to provide UNIX for the people out there. That meant providing BSD for the common hardware, the x86. It wasn't that they thought other platforms weren't good, or didn't deserve FreeBSD, it was (as I understand it) more a case of saying "We want to provide the best unix to the most people" and to devote their limited reources to small platforms was counter-productive.
    FreeBSD was never supposed to be x86 for the sake of x86, any more than Linux was (which started off in 386 assembly). It was (and is) x86 because that's where people most needed it. Despite running on many architectures, Linux is still most popular on x86. It's where the market is. FreeBSD is highly pragmatic - don't do it cause it's cool, do it cause it acheives a purpose.
    So, the conclusion then is, if the FreeBSD team feels that pouring some of the effort into a new architecture is going to provide greater overall benefit to the users, then it is within their original goals to do so.

    x86 was a starting point, not an end.

    --

  • I wonder how portable the applications are across all BSD platforms. While OS X is now built around the BSD kernel, there are Mac-specific extensions that developers must call to write programs for the Mac. The ultimate benefit of BSD-everywhere(TM) would be if applications required little or no modification to compile for the Mac OS or standard BSD system. It would be nice to see a host of FreeBSD applications that are simply ports of productivity apps for the Mac. The end result could be the acceptance of UNIX as a consumer platform, explicitly instead of implicitly.
  • No, read Part II of the interview - FreeBSD sees their mission as building a stable, functional OS for common desktops or "PC's", not Intel x86's. If/when other platforms attract users, it makes sense to make FreeBSD available there, too.

    I've been using x86 platforms for 15 years now (yow!) and must say that I'm pleased to see FreeBSD isn't tied to them - I think it's time to dump the old architecture and incremental changes to it, especially in light of the friendliness both Intel and AMD have shown towards user-hostile processor "features" like software-readable serial numbers.
  • by plastickiwi ( 170800 ) on Monday May 22, 2000 @03:47AM (#1057273)
    Can't you imagine the Apple commercials?

    "You are cordially invited to the marriage of frilly, fru-fru industrial design and the suave sophistication of an impenetrable user interface.

    "You'll be the first on your block to have a computer no one wants to look at *or* use."

    Every BSD iMac will come with a pocket protector and a black beret.

  • by Anonymous Coward
    The tone of the article seems defensive at times, and dream-like at others. Part of the fantasy is that FreeBSD can scale to a PDA. That really depends on how you define PDA. Unless there is an MMU available, you can't run FreeBSD on it-- which excludes most PDAs right off the bat.

    And the iMac? Most large corporations have moved away from proprietary hardware single-vendor ``solutions'' (love that word!). There is no indication that this trend will be reversed.

    The article is a good example of whistling past the graveyard. It fails to offer any realistic assessment of the operating systems marketplace, and FreeBSD's actual role in it. The reality and the fantasy of this article are way out of synch.

  • by Anonymous Coward
    I honestly don't beleive that Mac users will be willing to accept *BSD on their machines. Why? Let me explain. I have been using FreeBSD for about 6 months now, and find the printer support totally inadequate. The root of my problem is "lpd", the "line printer daemon" - lpd is OK if you own a line printer, but most people these days (myself included) own page printers. Hence, we are unable to print from our OS of choice, and have to reboot into Windows in order to use our laser printers.

    The iMac seems to have attracted a very fashion conscious user base, who like to be on the cutting edge of technology. I think these users in particular will be repulsed by having to throw out their shiny new laser printers in order to use an old, secondhand dot matrix printer. For these reasons, I think FreeBSD on the Mac will fail, until someone comes up with a ppd (Page Printer Daemon) for it.

  • Well, apple is rumored to have contributed to the ppc optimization of gcc, after all, they are using gcc to build macosX so this make sense
  • Command line BSD apps should have no problem running across platforms, once they're recompiled. Apps that need access to non-standard libraries won't run across platforms. For instance, you can't very well run Netscape on Linux unless you've got X installed. Likewise, you won't be able to run Mac OS X binaries on Free or NetBSD because they won't have access to the Carbon, Cocoa, or Quartz API's...

    And besides that, OS X isn't built around a BSD kernel, as far as i knew... I thought it was the Mach kernel running a BSD personality? Don't know if that makes much of a difference, though, except to further illustrate that OS-X and *BSD might be related, but they're definetly not twins or anything like that, if that makes any sense.
  • Are you on crack?!?

    Sun paid SCO nearly a billion dollars for the rights to SVR4!

  • You need to pipe your lpd jobs through ghostscript
    in order to print page oriented, graphical stuff.
    Check out a printing HOWTO or the FreeBSD manual
    for instructions on how to do this. It is more
    difficult than it should be, but once you learn
    how it is easy.

  • Amen to that. A Mac dual booting Mac OS and some *nix is my ideal system. I have Mac OS for when I just want to get things done without worrying about it, and *nix when I'm feeling geeky and in the mood to screw around (of course with Mac OS X I'll be able to both within one OS ;-)).

    I wonder how much of this decision to port to PPC is based on Apple's use of FreeBSD code in Mac OS X. Apparently Apple has been contributing back to FreeBSD on a regular basis, and I imagine has built a relationship with the FreeBSD people.

    --
  • you won't be able to run Mac OS X binaries on Free- or NetBSD because they won't have access to the Carbon, Cocoa, or Quartz API's.

    They can do Quartz/Cocoa once gnustep [gnustep.org] is done.

    "There's very little progress on GNUStep!"

    I assume this will see more progress as fellas will want to run their OS 10 apps without rebooting their boxen.

Don't tell me how hard you work. Tell me how much you get done. -- James J. Ling

Working...