Forgot your password?
typodupeerror
BSD Operating Systems

FreeBSD 5.0 Available 372

Posted by CmdrTaco
from the still-has-a-better-mascot dept.
Vegard writes "Although not yet officially announced, the 5.0 version of FreeBSD is beginning to appear on the FreeBSD FTP site and mirrors world wide." Congrats to the developers. Update: 01/19 17:44 GMT by T : Some more detail -- Dan writes "Scott Long of FreeBSD Release Engineering team has officially announced the availability of FreeBSD 5.0 release. Improvements include second generation UFS filesystem, GEOM, the extensible and flexible storage framework, DEVFS, the device virtual filesystem, Bluetooth, ACPI, CardBus, IEEE 1394 and many more! FreeBSD is also available on 64-bit sparc64 and ia64 platforms."
This discussion has been archived. No new comments can be posted.

FreeBSD 5.0 Available

Comments Filter:
  • Oh, hooray (Score:5, Insightful)

    by RPoet (20693) on Sunday January 19, 2003 @10:10AM (#5112880) Journal
    The release hasn't been announced, which would mean it hasn't reached the mirrors yet, which would mean they need the master FTP server to be up and running. How very convenient of Slashdot to link directly to the master FTP server before this has happened! This is sabotage.
  • Nice linking (Score:5, Insightful)

    by Openadvocate (573093) on Sunday January 19, 2003 @10:15AM (#5112896)
    Now why would you link directly to a FTP server? We all know that a lot of people will begin to download a +600MB ISO file and that no single FTP server would be able to handle the Slashdot crowd. Now I hope that the people here that wants to download FreeBSD has the brain power to check the mirror list first, if they not already has a favorite mirror. Still the proper thing to do, would be to link to the mirror list directly.
    Also by using the mirror list, our US friends wouldn't have to download from a server in Denmark, but maybe a local one instead. Oh, well I guess that's just me, but I really think that in the lengthly, time consuming screening process of each article, someone would show a bit of responibility, knowing the effects, posting a article with links have.
  • by BusterB (10791) on Sunday January 19, 2003 @10:29AM (#5112928)
    If you want NTFS support for FreeBSD, simply find a source of unencumbered documentation on that FS and let the developers know where you found it. Having trouble? I thought so!

    NTFS is intentionally underdocumented, so most attempts to support it in other OS's have been mostly reverse-engineering attempts. You could sign an NDA, but probably wouldn't be able to write free code with that information. Do not blame FreeBSD for not supporting undocumented features of another OS.

    If you have an example of any non-Microsoft OS that can install on NTFS, please prove me wrong!
  • by Anonymous Coward on Sunday January 19, 2003 @10:38AM (#5112953)
    Time and time again everyone says DO NOT LINK DIRECTLY to the main site, link to a mirror list. The fact that you still linked to the primary site and even said it has not been announced makes me wonder do you ever fucking read our comments. You guys need to develop a checklist before you post news items. 1. is it a dupe? 2. did i spell check this? 3. if there's a link to an product that was just released did i post the mirror link instead of the primary link? 4. And finally ask yourself this question, is this news the slashdot crowd really cares about? (*note this does not pertain to the current story)
  • Announcement. (Score:4, Insightful)

    by saintlupus (227599) on Sunday January 19, 2003 @10:44AM (#5112965) Homepage
    Although not yet officially announced

    Uh, maybe there's a reason? Like they want to finish pushing everything out to the mirrors?

    --saint
  • by cperciva (102828) on Sunday January 19, 2003 @11:00AM (#5113018) Homepage
    Quote from the 4.6 (non)release story [slashdot.org]:
    Murray Stokely writes "We have gone over this for the past 2 releases now. I thought I had made it clear that you were not to publish information about FreeBSD being released until you saw a signed PGP message from one of the release engineers. Are you trying to help the spread of trojanned copies of FreeBSD? The release is not ready yet, and will not be until the front page of FreeBSD.org is updated and a PGP signed announcement message is posted to announce@FreeBSD.org."

    Unless the rules have changed, slashdot screwed up again.
  • Early annoucements (Score:5, Insightful)

    by __past__ (542467) on Sunday January 19, 2003 @11:01AM (#5113019)
    I really wonder whether CmdrTaco is just too stupid to learn that a FreeBSD version is released when the release is announced by the release managment team and not when some files appear on some FTP sites, or if this has become some weird kind of personal vendetta or insider joke. Not only that he fucked up for every single release for some years now, they even started to announce release candidates early recently.

    Despite being idiotic, this behaviour is really harmful. FreeBSD takes care to let their mirrors prepare for the traffic peak when a new version is released. The early "announcements" on slashdot of course mean that the people managing the mirrors - voluntarily, people not only FreeBSD but lots of free software projects depend on - don't have this time to prepare, and might get major problems, which in turn might mean that they decide not to support FreeBSD and other projects by providing bandwidth for free any more.

    Unless this is some funky plan of VA Software or whatever their name is this week to push SourceForge, it would be really nice if slashdot could just stop damaging the Free Software infrastructure.

  • by vskjefst (455144) on Sunday January 19, 2003 @11:03AM (#5113025) Homepage
    If you don't want the public to spot your releases until they are officially announced, then you should keep them hidden. Upload your files with restricted access to the master ftp and all mirrors, issue the press release, THEN make the files public.
  • Re:A few mirros (Score:5, Insightful)

    by __past__ (542467) on Sunday January 19, 2003 @11:06AM (#5113032)
    Please look also if the files appeared on the other mirrors.
    No, please don't. Wait until it's released. The ISOs may still change without notice, destroy your computer and piss in your fish bowl. Say with me: These files do not contain a released FreeBSD version.

    And, of course, instead of downloading ISO images, consider using CVSup to save time and bandwidth. Or at least don't download all ISOs - you don't need all packages, and installing the stuff you want from the network works without any problems.

  • by root 66 (72128) on Sunday January 19, 2003 @11:08AM (#5113043)
    Would be great if those who already completed their downloads of the iso files could share them using their favourite peer2peer program to take some load off of the FTP servers.
  • by Tim C (15259) on Sunday January 19, 2003 @11:28AM (#5113126)
    They don't just do it to FreeBSD - any time any new version of a major piece of OS software is spotted on an ftp server somewhere, this happens. It has happened (iirc) for X, KDE, Gnome, Mandrake, etc.

    Sure, the maintainers could restrict access until everything is ready, then announce the release and open up the servers. But why should they have to?

    Jesus people, it only takes a little common courtesy to wait until the announcement is made. Is it really that important to scoop even the project's own site?
  • by Sycraft-fu (314770) on Sunday January 19, 2003 @12:04PM (#5113238)
    Uhh first off, I think the parent post is joking, making fun of moronic journalists. Secondly, pages 700-777 of "Inside Microsoft Windows 2000" (an MS book) provide a very good starter NTFS reference. Also the MSDN section on NTFS (http://msdn.microsoft.com/library/default.asp?url =/library/en-us/fileio/base/ntfs.asp) is another place to look. Finally, NTFSDOS is a third party, commercial, tool that allows DOS to access NT drives.
  • Re:Oh yeah ! (Score:5, Insightful)

    by b0r1s (170449) on Sunday January 19, 2003 @12:32PM (#5113361) Homepage
    But it's not a problem since many people said that it was better for me to stick with 4.7 and then switch to 5.1 or 5.2. Not a problem too since I'M on cable and I downloaded theses ISOs at 300+ kb/s :)

    This is a valid point that I haven't yet seen addressed: which is better for the average user, 4.7 or 5.0?

    There have been many, many changes to the code in 5.0, and there are bound to be more than a few bugs. If you're running a site that can have zero downtime, and you don't have redundant servers, don't bother switching to 5.0, it's simply not ready yet.

    If you're a home user, don't mind a few make buildworld, make buildkernel, make installkernel, make installworld sequences, upgrade. There's enough new that you'll enjoy it, and there's enough stability that you probably won't notice the infrequent bugs.

    If you're asking yourself "Why should I upgrade when everyone says there's going to be bugs?", the answer is simple: the bugs can't be found without testers, so everyone on the team needs your help to find them quickly. If you encounter a bug, file a PR, and maybe even try publicizing it on a mailing list. Letting the developers know that bugs exist is the first step in getting bug-free code.

  • Re:Nice linking (Score:2, Insightful)

    by SonOfSengaya (582624) on Sunday January 19, 2003 @01:19PM (#5113554) Homepage
    Yeah, because they just updated to 5.0...
  • MOD PARENT DOWN (Score:5, Insightful)

    by ChrisCampbell47 (181542) on Sunday January 19, 2003 @02:03PM (#5113787)
    Absolutely the only +5 comments on this thread should be people excoriating CmdrTaco for A) posting before PGP-signed announcement and B) linking directly to the master ftp site instead of the web page listing the mirrors.

    I mean, I expect this from one of the junior "editors", but Cmdr Taco? Come on.

  • Re:Release Notes (Score:5, Insightful)

    by Twirlip of the Mists (615030) <twirlipofthemists@yahoo.com> on Sunday January 19, 2003 @02:35PM (#5113956)
    Some companies [apple.com] are already well aware of the benefits of the BSD license. The net result? One company [apple.com] is now the largest single producer of UNIX operating systems in the world, measured in terms of number of units shipped per year.

    The BSD license is a beautiful thing. Software that carries the BSD license can really, seriously, no-shit change the world for the better.
  • by Blkdeath (530393) on Sunday January 19, 2003 @05:43PM (#5114871) Homepage
    If you don't want the public to spot your releases until they are officially announced, then you should keep them hidden. Upload your files with restricted access to the master ftp and all mirrors, issue the press release, THEN make the files public.

    Thank you for that.

    I just have one thing to add here;

    I've been reading all these comments from the BSD crowd here in awe. I mean, all this hostility over... what? An announcement that linked to a PGP-signed release announcement. The ISOs are on the servers. The time to rejoice is nigh! But no rejoicing from this crowd. No "Awesome new features ... I can't wait to test this on my home rig ... " postings; just adolescent whining.

    Seriously folks; you respect the FreeBSD development team, right? You respect their programming talents and their combined decades of computer, operating system, and networking experience, right? Do you really take them to be this naive? Would you really have us believe that they would roll release-grade, Version 5.0 (no RC-*) CD images and make them public when they weren't ready? Do you really think they'll be at all SURPRISED when people start to notice, download, and tell all their friends about this release? Don't you think they have a solid, stable (FreeBSD) FTP server pumping out these requests, properly configured with reasonable user/transfer limits in place, and QoS on their upstream bandwidth? If you're that unsure of FreeBSD's ability to handle high loads - why are you downloading it?

    It was inevietable that this would find its way to Slashdot. That's how Slashdot works. It's been seen time and time again. KDE, GNOME, Linux Kernel, XFree86, [Open|Star]Office, or any other project of significant magnitude (and interest) - the release files are made publically available, someone notices and the Slashdot editors respond to the influx of "It's here! It's here!" submissions. As a result, Slashdot is very often the first place to find out about new software updates. Is this really 'news' to anyone?

    Sure, they could link to the mirrors, but not doing so isn't by any means a conspiracy, it may be poor taste, but it's the same taste that links directly to kernel.org when a new Linux kernel is released. It's been pointed out to me more times than I can count that Slashdot readers are "IT professionals" - so stop talking about being professional and act like it. Download reaponsibly; use a mirror.

    I'll download a mini-ISO later, when the tide has ebbed, and install it at my leisure.

    </RANT>

  • Re:Nice linking (Score:3, Insightful)

    by axxackall (579006) on Sunday January 19, 2003 @08:19PM (#5115673) Homepage Journal
    if journalling is just a hack, why IBMuse it instead of UFS? I don't believe that journalling is just a hack. It's reliability has been proven by several new-designed open source and commercial filesystems: ReiserFS, XFS, JFS.

    As for Ext3, it's been improved, not hacked. And counting its age it's already reliable. Compare to UFS back to the same age.

    As for scaling, I doubt that IBM made a mistake choosing Linux as a replacement for AIX. Otherwise, why IBM did not do the same or similar step as Apple did? The answer is simple: IBM doesn't trust to non-scalable design of BSD.

    Recent news from SGI (Linux on new SGI servers) just proves it.

  • by Anonymous Coward on Sunday January 19, 2003 @08:22PM (#5115686)
    Unfortunately: GEOM is for layout of block devices (e.g. at the partition & sector level), not for virtual filesystems. It has no concept of directories and files.

    *BSD already has a virtual filesystem layer in the kernel, but it's not accessible from userland.

    JJ

A failure will not appear until a unit has passed final inspection.

Working...