Slashdot Mirror
FreeBSD 5.0-RC1 Now Available
Dan writes "Murray Stokely of FreeBSD release engineering team announces that they're one milestone closer with the immediate availability of FreeBSD first release candidate for the i386, alpha, sparc64, and ia64 platforms. ISO images and FTP installation directories are available now from the FreeBSD FTP site."
Murray Stokely of FreeBSD release engineering team announces that they're one milestone closer with the immediate availability of FreeBSD first release candidate for the i386, alpha, sparc64, and ia64 platforms.
So what are you saying here? That FreeBSD has never been released before?
But does it run Linux?
FreeBSD releases you!
Look it moves... It must be alive!
great, I just installed 4.7 last night...
try looking for yourself at freebsd.org maybe?
it's just a thought
...because those Linux folks started to get to culty--kinda like the Mac people.
Wasn't it released this summer?
I remember downloading a 5.0 ISO and I am sure it was RC1, but then again I might be wrong.
I have 4.6 running in our office, never had any problems, but with all the talk of the improvements, I'm tempted to upgrade.
Is this stuff ready for "prime time?"
Location: Mt. Xinu
Here's a direct link to the pertinent section. It details kernel, userland, and security updates that have gone into the 5.0 tree of FreeBSD.
If you celebrate Xmas, befriend me (538
BSD is dead?
BSD sux, Linux rocks!
"I switched to FreeBSD and was amazed..."
"I tried FreeBSD and it sucked..."
"Not to troll, but why should I use FreeBSD instead of Linux"
FreeBSD and SMP sucks!
"In Soviet Russia, the RC1 releases YOU!"
"BSD != DEAD"
So you se my friends, no need to post further! Thank you, come again.
I don't know whether you're just a troll or unclear on basic concepts, but you're wrong on multiple counts. 802.11b cards are well-supported, and journalling is a band-aid for a filesystem. FreeBSD's filesystem is well-designed and doesn't need that band-aid. As for token ring, ehh...
Isn't it great how people can release things for hardware you wouldn't even know how to buy if you wanted to. I've often wondered how elements like the FreeBSD team and Linux get people interested in doing these things. Its not like an "itch you need to scratch" because you don't even have the body part to have the itch on!
An Eye for an Eye will make the whole world blind - Gandhi
Have they fixed all the performance/stability problems yet?
or does it?
I mean decent ones?
Look at the title on the link you provided. FreeBSD/i386 5.0DP2 Release Notes. Meh.
I for one am very glad to hear about this.
This release promises a whole new freebsd kernel. I hope it brings them success. Congratulations on the hard work guys.
"If a show of teeth is not enough, bite
Should be basically the same as RC1 though considering DP2 and RC1 are basically the same set of code just with a different name.
SMPng: The next generation support for SMP machines (work in progress). There is now partial support for multiple processors to be running in the kernel at the same time.
KSE: Kernel Scheduled Entities allow a single process to have multiple kernel-level threads, similar to Scheduler Activations.
New architectures: Support for the sparc64 and ia64 architectures, in addition to the i386, pc98, and alpha.
GCC: The compiler toolchain is now based on GCC 3. X , rather than GCC 2.95. X .
MAC: Support for extensible, loadable Mandatory Access Control policies.
GEOM: A flexible framework for transformations of disk I/O requests. An experimental disk encryption facility has been developed based on GEOM.
FFS: The FFS filesystem now supports background fsck (8) operations (for faster crash recovery) and filesystem snapshots.
UFS2: A new UFS2 on-disk format has been added, which supports extended per-file attributes and larger file sizes.
Cardbus: Support for Cardbus devices.
was the adoption of a new method naming scheme in the kernel. Now all functions are in hungarian notation for extra speed. If you look at the page scheduler code and squint you can just barely make out an image of Bill Joy creating intellegent killer robots that will destroy the world.
A major improvement in FreeBSD 5.x over 4.x is the new modular init. Instead of one monolithic script (classical BSD) or several scripts in a symlink farm with manual sorting and dependency resolution (SysV / Debian, RedHat, SuSE...), it uses an internal automatic sorting and dependency resolution comparable to apt-get or modprobe on GNU/Linux. I would like to see mainstream adoption of this in the GNU/Linux world of this. To date, Gentoo Linux is the only distribution offering and supporting this excellent feature.
gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
GBDE ROCKS!
How is it obvious that BSD is dead? The BSD's are as popular as ever.....
Please, give us some proof.
02-12-09 14:33 BSD: FreeBSD 5.0-RC1 Now Available
My monitor sometimes thinks it is a crystal ball; using it I can predict future /. headlines. Here goes:
03-01-06 9:25 BSD: FreeBSD 5.0-RC2 Now Available
03-01-14 9:25 BSD: FreeBSD 5.0-RC3 Now Available
03-01-25 9:25 BSD: FreeBSD 5.0-RC4 Now Available
03-02-02 9:25 BSD: FreeBSD 5.0-RC5 Now Available
03-02-17 9:25 BSD: FreeBSD 5.0 Released
03-02-19 9:25 BSD: FreeBSD 5.0.1 Released
Funny thing though, apart from the different version numbers the discussion is always exactly the same...
Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
You must be missing the concept of Filesystems... All high performance filesystems have some kind of "journal" (sometimes called differently) implemented in one way or another...
Vinum has not been mantained at a high level for some time and I have heard that there is a replacement in 5.0 that emulates the IBM AIX volume manager (which kicks ass in my opinion).
Any word on this?
Either give it away or get top dollar, but never sell yourself cheap.
Hahaha. Idiot. You clearly have no notion of atomicity. A journal is a band-aid, nothing more. Do some reading before spouting from your mouth, okay?
No, come on people, it was funny this time. Normally the reversal of the 2 things doesn't make any sense, but FreeBSD releases you does, and is amusing.
IT IS AMUSING YOU WILL LAUGH.
graspee
As a note to the curious, the Linux compatibility improved "greatly" in the latter half of the 4.x series. It's more likely that one or two simple functions were fixed (I haven't followed closely, and it's been a while), but this means that previously tempermental software- the Amiga/Elate SDK, for one example- now runs flawlessly as of 4.5 or so.
;)
Loki games should be no problem, not that they were before.
I don't know whether to mod this +1 Funny or +1 Insightful.
I was going to say...not necessarily support I'd be looking for. Unless of course you're going to build a DNS server - you know, one server to rule them all, one server to BIND them...
I want to delete my account but Slashdot doesn't allow it.
... The domain name freebse.org isn't registered yet... :D
I tried to get DP-2 working in Virtual PC but networking seemed to get stuck. Anyone have luck with getting FreeBSD to work in Virtual PC? Are there patches that need to be applied?
Dude, you're just wrong.
What tag= should I use in my cvsup conf file to update to this wonderful release? stuf.f
Jace is cool.
Daniel Bendorf
nt
any real reason for even releasing an ISO? according to the sparc64 page, it is completely crippled, not keyboard or mouse support,no video support and no floppy support. So is this a blank iso or what?
The next time I buy a computer, it will have a 64-bit processor. Since ia64 is what FreeBSD seems to be supporting, and I have never had a problem with Intel, that is probably what I will get. There doesn't seem to be any real wok done on AMD's 64-bit chip for FreeBSD. You can actually buy an ia64 currently, whereas AMD's is coming "real soon now." The last time I purchased an AMD (about ten years ago) it ran about half as fast as the supposedly equivalent Intel chip. I honestly don't know why so many people have such a love of AMD. I am glad that Intel has competition, though. The main reason why ia64 is having troubles is because not much supports it yet. Once FreeBSD gets a usable ia64 port, it will just be a matter of time for any other OS that wants it.
Best Slashdot comment ever
Mac OS X 10.2, being a hybrid of FreeBSD, does already support some features coming with FreeBSD 5 (such as SMP), but OS X does not use BSD 5.0, yet.
According to Apple's OS X 10.2 System Overview, Mac OS X 10.2 is based on 4.4BSD subsystem elements. This was an update from, I believe, 3.3BSD support in 10.1.
Apple is careful not to get experimental with their production operating systems, although it a safe bet that somebody at Apple is continually testing new configurations from FreeBSD development builds.
FreeBSD 5 will have to show its mettle before Apple officially integrates the 5.0BSD subsystem in a later OS X update.
Vos teneo officium eram periculosus ut vos recipero is.
You can help by getting off your rear and writing to your congressman or senator. Tell them FreeBSD is important to you. Tell them that without FreeBSD, you would have to find less managable and intelligently designed alternatives. Let them know that this is an issue that effects YOU directly, that YOU vote, and that your vote will be influenced, indeed dependent, on his or her policy on FreeBSD.
You CAN make a difference. Don't treat voting as a right, treat it as a duty. Keep informed, keep your political representatives informed on how you feel. And, most importantly of all, vote.
KMSMA (WWBD?)
FreeBSD has grown larger and larger -- back in the 3.x days I could run it easily. The 4.x series have consumed much more memory, even when the kernel is compiled to use the same features. I had heard that one of the 5.x trees goals was to regain some of that "thin" nature which IMHO is one of FreeBSD's biggest draws. Anyone know how that is coming along?
MORTAR COMBAT!
Is there a release roadmap, guessing when 5.0 final and 5.1 will come out? I haven't seen it on the FreeBSD site.
I know everyone was saying how better and more secure BSD is, but didn't we hear how RC5 was cracked? Why the heck would I want RC1, then? ;-)
Vinum has not been mantained at a high level for some time and I have heard that there is a replacement in 5.0 that emulates the IBM AIX volume manager (which kicks ass in my opinion).
Will it also have a journaled filesystem that is growable while mounted and users are accessing it?
The last time I purchased an AMD (about ten years ago) it ran about half as fast as the supposedly equivalent Intel chip. I honestly don't know why so many people have such a love of AMD.
so really you dont know wtf u r talking about.
2ghz PIV 2ghz Athlon price
whats not to love
Mods: Please mod +5, Kiss My Ass. Thanks ;)
Somebody told a biologist that "BSD is stable" and
they drew the wrong conclusion.
Ben "You have your mind on computers, it seems."
MPlayer works on FreeBSD. So now, you can run your favorite OS with your favorite media player. So shut up, shithole.
UFS2 Anyone?
Unhappy about how your VA Linux stock did?
It crashes if you eject a floppy disk without unmouting it!
Actually that means its not fault tolerant... :) You are the unstable one who ejects things without unmounting them.
The kernel does panic if you try to mount a CD that wasn't fixated though... or at least it did back in 4.6. That is the same kind of fault intolerance as the floppy eject thing I bet.
...RELENG_5, for "5-STABLE," or perhaps RELENG_5_0, for "5.1?"
t ml carries some hints; I can't say I've ever found the CVS layout fully documented, myself, though I'm also as much a moron as all of you are. ;)
/usr/src if it's not right.
http://www.freebsd.org/releases/5.0R/schedule.h
Try a cvsup and see what you end up with; rm
The arguments of a person with such a "flexible" version of the English language tend not to change my mind.
Best Slashdot comment ever
The base install should allow for boot scripts, minimal drivers, and system binaries. Try using the FreeBSD installer to install a system onto a 64 MB flash IDE drive, for instance -- you can't, because the base system takes up too much space. RAM really isn't the issue, although "whopping" 16 MB is fairly whopping considering the target audience.
MORTAR COMBAT!
Actually, I've had no problems with x.0-RELEASEs. We installed 3.0-RELEASE on our machines the day it was released. We were waiting for it because we needed support for our SCSI card. This was before I knew about -SNAPSHOTs. Anyway, we installed it and ended up running it for like two years without a reboot. I remember a few security issues that could be patched while the machine was running but I don't remember any showstopper stability issues or system corruption issues. In fact, in all the releases that I've installed since 2.something-really-low, I don't think I've ever seen an unstable or dangerous -RELEASE.
Now that FreeBSD has cardbus support can we expect Apple to grab some code and improve their cardbus support. While Apple's CardBus support does the basics there are many drivers that I have heard could not be written simply because the API support did not exist. Is this something Apple can grab. I'm not funny up to date on what Apple grabs from which various BSD projects. -Tim
Tim Smith - Ramblings from Nerd Land
Our lifehood depends on using Win4Lin to run our Windows application.
Does FreeBSD 5.0 run Win4Lin? Thanks a whole lot.
I tried FreeBSD, and found the cult mentality to be very much in evidence. That, plus the FreeBSD credo of "if it was hard to write, it should be hard to use" drove me back to Linux. If they lose their elitist attitude, maybe I'll try it again some day when Linux can't do what I need. Right now there's no reason at all for me to switch.
Yeah, there's DVD players available for FreeBSD.
Fuck off dipshit. FreeBSD sucks - just like you do. Keep on sucking those dicks boy!
I can't comment on what AMD was 10 years ago, but last year AMD certainly where the best x86 CPU you could get. Even know they are still really good, although the very high end P4s do have an advantage.
But on price/performance, they are still very very good.
But how is your comment about AMD 10 years ago relevent now? The computer industry changes in 10 months, let alone 10 years. The fact that AMD still exist is enough of a sign that AMD are doing well.
Just because AMD were bad 10 years ago, doesn't mean they are now.
This is true, but it does increase the probability greatly. Generally, whenever I have a problem with a company, I make a point not to buy from them again. I had an AMD 486DX4 100MHz and an Intel 486DX 66MHz, and the Intel chip was noticably faster, in practally identical systems otherwise. It isn't the slowness that annoyed me (it did cost less), but the fact that they claimed otherwise.
Best Slashdot comment ever
Fuck off BSD loser! Eat your smelly feet hahaha!
Damn, did your Linux box crash yet again, taking up too many resources or just simply is a pain in the ass?
If I cared about a list of friends, you'd go on it for that post alone.
Please do us a favor, and die. Thank you.
--- The Rest of Slashdot
The next chips out of Intel IA2 (or whatever) will be largely based on the Alpha chip from DEC-now-Compaq-now-HP. The Alpha is pretty good product victimized by absurdly stupid management/marketing/pick-what-you-like. So it's a worthy question. Why support a POS architecture when the successor, due out in another year (GA), is vastly different? It may be a lot of work that won't translate over well.
Computer Science is Applied Philosophy
can i download a service pack to upgrade?
free (as in mp3s) electronic music
You must mean "kldload GNU/linux ; ./sick-GNU-linux-binary ; rejoice!"
Can I get an eye poke?
Dog House Forum
> Real OS's shouldn't need cartoon character mascots.
Right! They should have pudgy guys dressed up in blue butterfly outfits!
Chris Mattern
10 years ago, everyone was running DOS, so it increases the probability that we're running DOS today, right?
Take some statistics classes and get back to us on that one.
I think maybe it would be timely to start using "z-index" for posts on Slashdot, such that meta-comments, like the one I am replying to would float above one layer. This post of course, would have a z-index of 2, being a meta-meta-comment. Self-referential posts (like this one; I just upgraded) may cause cool "tunneling" effects on your monitor due to infinite recursion.
Please... I'd bet any money that if a journalled file system became available for BSD and announced on slashdot, idiots like you would be foaming at the mouth and cumming in your pants with pure pleasure, spouting the virtues of BSD.
The next chips out of Intel IA2 (or whatever) will be largely based on the Alpha chip. . .
Do you have any links to back that up? That would be the coolest thing in the world, but from what I've read recently HP is burying Alpha and PA-RISC in favor of Intel's Itanium, and that Intel has some of the technology from Alpha but apparently can't just take off with a new line of Alphas by themselves.
You sir are the idiot. FreeBSD's filesystem isn't atomic. It is simply updated in a sequence that causes known and easily fixable inconsistencies. Look at *databases* if you want to talk about atomicity - oh dear, most of them use journals (logs, WALs, etc), looks like your argument just went to the shitter.
...and both of which implement the IA-64 architecture. The FreeBSD port isn't to Itanium I, it's to IA-64, so it should be able to work on Itanium II as well (although there may be work needed if Itanium I and II different in any ways not covered by the IA-64 architecture spec that matter to the OS).
They may use similar implementation techniques to ones used in various Alphas (there's no such thing as "the Alpha chip", there are multiple Alpha chipsinstruction set architecture will be dropped in favor of an ISA similar to Alpha.
I have seen nothing to indicate that the successor will be "vastly different" in its instruction-set architecture, so that work done to port to Itanium I-based machines "won't translate over very well" for Itanium II-based machines.
Okay Okay apologies.. Jesus.
Look at all these BSDers attacking me. I was wrong about the filesystem, but it would still be nice to have a journal on it. I HAVE lost files in FreeBSD due to buggy oltr driver crashing the kernel.
Secondly my main point was lack of TR support. Is anyone here going to contest me about this?
Thirdly I mentioned "Linux trailblazer with featues" which is something FreeBSDers cant deny. At the cost of some stability they HAVE something that runs on Ericsson phones and IBM pServers, and is fast pushing to become a Desktop OS. I tired FreeBSD for the sake of simplicity and stability, and in these arenas I remain satisfied. Only my requirements changed and I need both TokenRing and ArcNet support. My com90xx card which is running in Linux wasnt detected in FreeBSD, TR was a disaster since the driver is so alpha. This is why I was "hoping" for more drivers and framebuffers, DRI, soundcards, HPOJ laserjet printer etc. So instead of flamebaiting FreeBSD elitists, I'll just sit tight in a corner, wait till FreeBSD gains these features and then reinstall it.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
FreeBSD 4.5 works fine with both my mouse and keyboard so I know its a bug.
http://saveie6.com/
VMware uses /proc (or rather, /usr/compat/linux/proc ;-)
/proc.
/proc from tape, rendering it totally useless for me as a file system. But then again, I'm not a plan 9 fan either, which probably makes me a heretic in many UNIX users eyes.
This is Evil, I quite agree. But from what little research I've done, even a getppid() call on Linux seems to involve opening
I only wished mount had an option to make a file system visible under emulation only.
Last I checked, I was unable to restore
Native VMware support for FreeBSD is when I unzip my purse again. I have a hard time believing it'll take more than a day or two for a VMware engineer to fix up the fallout from a "make World" on FreeBSD. Oh well. I think too many FreeBSD users overestimate the engineer/marketer ratio at VMware, and I believe they'll have a hard time getting an engineer off his proverbial to do such a port, and train the support staff ("look, when you tell the user to type "uname -a" and he mentiones FreeBSD, go to page 5 of your cheat sheet"). I'm only half joking there; educating the support staff is an important job, and while I feel VMware support is less than stellar, I challenge any commercial operation to do a better job (or Plex86 to come up with a better Open Source equivalent, FWIW, and I sure lack the time to assist there).
Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.
Right now there's no reason at all for me to switch.
Hey, if Linux does the job for you, why switch? One mans elitist stance is another mans sign of quality. And vice versa. I think that if you look around in the Linux world, you'll find that Debian is much closer to FreeBSD, than Redhat is. If you look around in the BSD world, you'll find that FreeBSD is much closer to Redhat than NetBSD is.
All are excellent OSes. If it were anything near practical, I'd be multibooting Linux for productivity apps, FreeBSD for server development, NetBSD for kernel development, Debian for server deployment, OpenBSD for security critical stuff, Win98 for games and Win2k for Windows support. All of them tasks I perform at times. Stuck with limited disk space and the annoyance of reboots, I use FreeBSD for work and Win98 for games. And I payed the Microsoft tax for the games. So sue me.
As Opus so eloquently put it, "to each his dentifrice".
Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.
(I'm not aware of any pthreads implementation being of the "npw" variety, so I changed the subject to match what I think the original poster intended -- but then again, the _np suffix has bit me more than once in the past, so there very well might be a Non Portable Windows standard by now, pardon my ignorance).
Or you asking about kernel threads?
I still see pthreads as a programming convenience, and as such, FreeBSD pthreads has served me very well.
Once you get to serious pthreads programming, all but a few commercial implementations fall flat on their face. Needless to say, to support those Serious Programming efforts, those commercial implementations generally do not rank highly on performance, as all that multi-CPU stuff more often than not eats CPU time in spinlocks, and most apps that on the surface could do with multiple CPU's turn out to be disk bound in the first place.
It is so rare that I see apps that actually would benefit from multiple CPU's that I'm consistently stunned to see this issue receiving attention from folks who are not doing fluid dynamics or some other highly parallelizable task.
Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.
If you're happy with Linux, why not stick to it?
I wouldn't dream of running my FreeBSD boxes with unproven drivers. I hate being stuck with a DVI Geforce4 card driving a DVI LCD (even though I have reason to believe the Xfree86 support on Linux would suck as badly). If weird device support were important to me, I'd be running a flavor of Linux by now.
And I hate all of the parochialism as much as you do. Trust me, I shed many a tear over the unavailability of a native FreeBSD port of VMware. But I cope with it because FreeBSD serves me better in other respects (and most of them immaterial -- my main dislike for Linux stems from the default colorized ls in Linux 0.something, back in the days when the whole install fit on te floppies).
Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.
There is in fact support for token-ring, the oltr driver is being used successfully by many people.
If you have problems with the oltr driver why don't you stop whining about it and submit patches to make it better? You could at least post questions to the token ring support mailling lists offered by FreeBSD. I have not heard of any problems with token-ring and filesystem corruption.
Madge bought Olicom's token-ring division and is now selling Madge cards with Olicom markings, chances are that is what you bought and why you had problems.
In fact you are flamebaiting, but it looks like a habit. Stay on Linux, don't read BSD articles and we will all be happier.
486DX4 100 = 25 Mhz bus
486DX 66 = 33 Mhz bus
Hmm, which one looks quicker to you? Those of us that understand computers would pick the faster bus. Just because you don't understand computers doesn't mean AMD sucks. The AMD 486 was an exact clone of Intel's.
Colours in 'ls' help you spot things quicker. Colours are helpful as an indicator to us (think traffic lights). It might be a personal dislike to you but nicely tuned colourisation in ls does help you navigate and perform your tasks easier. Our eyes 'see' colours for a reason, why not deploy them in an environment in a way beneficial to us?
Journaling has nothing to do with "band aids." Journaling makes sure that if a system suddenly loses power it can recover its file system. By keeping track of changes BEFORE making them, the FS can look at where it was last planning to change and, if something's wrong, change it back to what it used to be.
Despite flexible language usage he does have a point: current Athlon chips compare favourably with their Intel equivalent. Certainly any given Athlon is a lot faster than the P4 you could buy for the same price. Maybe if Intel pushes ahead with higher and higher P4 clock speeds, AMD will return to the position of being the slower, cheaper alternative - but right now it's competitive both in price and in performance, at least at the non-insane-cutting-edge-early-adopter-price-gougin g end of the market.
-- Ed Avis ed@membled.com
If you have problems with the oltr driver why don't you stop whining about it
Read the title of my post. I'm 'hoping' it gets the driver support on Linux's scale. This is'nt whining.
I shopped around and specifically bought an Olicom 3140 which I saw in LINT to use TR in linux. So yes, I know oltr exists and in alpha stage. This setup worked for over a year under heavy loads, but I still cannot take a crash a month on a production server. I'm not blaming FreeBSD, I'm blaming the flaky driver.
Yes I subimtted bug reports. Apparently not many people are working on it so there.
Run linux happily? I installed FreeBSD in the first place because I was happy with it and most of its functionality and stability over Linux and Solaris.
I know BSDers (I've always considered myself one too) have gotten very itchy over remarks over its shortcomings. Theres nothing really to flame about especially over expressing hope over its future developments. Read the comments posted again till you realize theres no reason to attack me. I gave full due credit to FreeBSD and Linux where they deserved.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
It might be a personal dislike
It is a personal dislike, and not even fully rational. I just don't like it.
nicely tuned colourisation in ls does help you navigate and perform your tasks easier
I never saw a nicely tuned color config. As a matter of fact, the default ls color scheme, and the default VIM color scheme hurt my eyes to the point of distracting me from my work.
Color is overused and underutilized. IMHO.
Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.
You got me. This was told to me by HP/Compaq sales folks at a presentation. They're trying to get into the company where I work and we're talking about their migration plans. I'll look and see if I have any soft docs...
Computer Science is Applied Philosophy
It was made to sound that the only real similarity will be in name. This says somethign drastic to me, I could be mistaken
Computer Science is Applied Philosophy
And there's probably not much (if anything) left of the P6 core (Pentium Pro, Pentium II, Pentium III, many Celerons) in the Pentium IV, and not much left of the P5 core (Pentium, Pentium MMX) in the P6 core - but they all implement the x86^H^H^HIA-32 instruction set, albeit with various additions over time (MMX, SSE, and assorted other stuff such as conditional moves and a 64-bit compare and exchange).
The Itanium 2 implementation of the IA-64 instruction set might not share much with the original Itanium implementation IA-64 instruction set, but that doesn't mean that they don't implement the same core instruction set.
In fact, the Intel FAQ on Itanium 2 explicitly says:
(emphasis mine).
it seems that 4.7 and probably 4.6 install floppies don't work for alpha - they panic
as soon as dhclient gets an IP, it seems.
time to go try the new version
there are many knowlegable geeks that are available for free tech support here