Slashdot Mirror
FreeBSD Boots on x86-64
craig2787 writes "FreeBSD developer Peter Wemm has successfully booted FreeBSD on a real AMD ClawHammer CPU, in both 64- and 32-bit modes. Original posting to the -current mailing list is here."
← Back to Stories (view on slashdot.org)
"CPU: AMD ClawHammer(tm) (3.14-MHz Hammer-class CPU)"
3 Megahertz? Whoohoo, looks like AMD is giving the Intel a run for it's money... and MOS, too.
Seriously, though, I'd eventually like to see some real world performance specs of Hammer running in 32 bit mode, just to see if it's going to suffer from the same 32-bit-on-64-bit problems that Itanic has been having. If they figured out a way around that, they could totally own the market because Itanium 1 is dead and all cursory tests on Itanium 2 show it sucks the glands of a large braying animal when it comes to 32 bit code.
Hilary Rosen's speech was about her love of money and her desire to roll around naked in a pile of money.
if FreeBSD is dying, it's dying in style? ;-)
Yes, Freebsd beat Linux'$ butt again
I think I know what computer I'm saving up for next.
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
Looks like OSS and AMD will be leading the cheap power realm for time to come...
projects @ http://spectechnologies.net
*BSD is no longer dying but now is nothing but an urban myth.
Becuase I've never seem *BSD I'm concluding that it doesn't exist. How many have been tricked?
*BSD the OS that isn't.
Peace.
I didn't get any free BSD boots on my computer.
You've definitely got to hand it to BSD; it seems to be able boot on just about anything. One look at NetBSD's home page makes this obvious. :)
This added compatability is not only good news for BSD users, but also for the whole open source community, which doesn't seem to have any trouble keeping up with new technology.
FreeBSD has focused on Itanium up until now, given that production hardware has been available for a while. There are people who already have them in their datacenters and who want to run FreeBSD on them. It's part of the pragmatism that is at the base of FreeBSD's philosophy.
NetBSD has more of a research-focused, "climb the mountain because it's there" philosophy. Compare mottos: "FreeBSD -- The Power To Serve" vs. "Of Course It Runs NetBSD." That's not to say NetBSD doesn't make a fine, practical embedded platform (say), or that FreeBSD is useless in research (especially when that research can result in improved performance in the datacenter, FreeBSD's home turf). It's just a difference in emphasis, and the BSD community is richer for it.
I love free, open source software!
BSD, Linux and GNU put most other software to shame.
Way to go guys!
I agree with the FreeBSD principle. I started with NetBSD because FreeBSD had a bug for my setup about 1-2 years back. It couldn't handle a Master-slave HDD relationship, used to freeze with "Probing devices please wait" on a i386.
And I find FreeBSD's documentation to be the best amongst the three.
Thanks for the clarification.
Perhaps it would be possible to spectate chartres with highest graphics and supported resolution! YEEHAW
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It'
Because you can cluster BSD as well, can't you?
*unsure and confused since there arent any cluster-remarks*
Not Buzzword 2.0 compliant. Please speak english.
FreeBSD Boots? Where can I get my pair?
Will it keep my feet warm with that x86-64?
My exception safety is -fno-exceptions.
Now, I'm not denying that what this guy is done is pretty good. But if you can't even get to /sbin/init, then has your system really booted up? Certainly not in any useful way. I think this story is a bit premature. Post another one when programs can actually run on FreeBSD on a Clawhammer. Only then will I really be impressed.
send me ur old system.pls.
Lord of the Binges.
soon as i get the new one booted
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
# portant Stuff: Please try to keep posts on topic.
./rdesktop server. For information on command line options, try ./rdesktop -?.
# Try to reply to other people's comments instead of starting new threads.
# Read other people's messages before posting your own to avoid simply duplicating what has already been said.
# Use a clear subject that describes what your message is about.
# Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
# If you want replies to your comments sent to you, consider logging in or creating an account.
Problems regarding accounts or comment posting should be sent to CowboyNeal.
OSDN | Development
(Note: only the characters 0-9a-zA-Z_.+!*'(),-\$, plus space, are allowed in nicknames, and all others will be stripped out.)
Nick Name
Email address to send your registration information to. This address will not be displayed on Slashdot without you setting your preferences to display it.
Real Email
Replies to my comments will be mailed to me
Send me the newsletter
Send me the daily headlines
To confirm you're not a script,
please type the text shown in this image: (random letters)
Click the button to create your account and be mailed a password.
Log in to Slashdot.
Forget your password? Have your password mailed to you by entering your nickname, uid, or email address.
Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them?
All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2003 OSDN.
[ home | awards | contribute story | older articles | OSDN | advertise | self serve ad system | about | terms of service | privacy | faq ]
rdesktop: A Remote Desktop Protocol Client
for accessing Windows NT Terminal Server
Overview
Status
Download
Mailing Lists
Documentation
Overview
rdesktop is an open source client for Windows NT Terminal Server and Windows 2000 Terminal Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user's NT desktop. Unlike Citrix ICA, no server extensions are required.
rdesktop currently runs on most UNIX based platforms with the X Window System, and other ports should be fairly straightforward.
rdesktop was written by Matt Chapman (matthewc@cse.unsw.edu.au) based on various scarce documentation, wire sniffs, and trial-and-error. It is released under the GNU Public Licence (GPL). Please send feedback, bug reports and patches to the appropriate mailing list. Patches can also be submitted to the SF patch tracker.
rdesktop is a SourceForge.net project. See the Sourceforge rdesktop project info for more information.
Status
The latest stable version of rdesktop is 1.2.0. This features new keyboard mapping code, high encryption support and many small additions and bugfixes. We are now working towards RDP5 support.
Download
Stable versions
rdesktop 1.2.0:
Source (123 KB)
rdesktop 1.1.0:
Source (80 KB)
rdesktop 1.0.0:
Source (48 KB)
Experimental Patches
CVS access
See the CVS instructions. Note that the CVS version may be unstable currently as we are working on new features.
Mailing Lists
We have migrated our mailinglists to SourceForge - click here for the available mailing lists.
The archives of the old mailing list are available at http://mail.rdesktop.org/archive/
Documentation
There is currently no documentation for rdesktop aside from this web page. Simply running make should be sufficient to build rdesktop; then run
The RDP protocol itself is essentially an extension of the ITU-T T.128 (aka T.SHARE) application sharing protocol. While as far as I know there i
slashdot is a magnets for idiots, period.
Oh the no reboot things holds true for
my sparc/linux firewall as well.