Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Red Hat Software Businesses

Red Hat 7.0 Beta Is Out 358

Thorkild writes: "The subject says it all. They just opened up the directories on the mirror sites." If you can't find it without me telling you where it is, then you shouldn't be running a Beta Red Hat 7.0 ;)
This discussion has been archived. No new comments can be posted.

Red Hat 7.0 Beta is Out

Comments Filter:
  • Also, since we're using gcc 2.96

    I presume thats a carefully selected snapshot.

    Has the IA32 c++ ABI been finalised (and implimented), or will there still be one more round of c++ program breakage?

  • I like to download slightly buggy debian packages and write to an author and say, "hey, this is a little bit messed up"

    Sure, we listen to those, as well. If you don't want to use bugzilla for whatever reason, just pick the latest name in the changelog.
    Chances are you'll get a reply, even if it takes a while (we get a lot of them, I'm admittedly about 500 mails behind at the moment).

    I also like a minimalist base install

    We've fixed that up for 7.0. (Pick custom install and select individual packages, then don't select anything).
    We're down to 30 or so packages in a minimal install.

    Why do distros feel the need to come with a shitload of software?

    In some countries, net connections are terribly expensive, and the average computer store (unfortunately) still doesn't carry a lot of Linux software or mirrors of Linux ftp servers, so we're better off including a lot of things.

    Including it on the CDs doesn't mean you have to install it... That's what custom installs are there for.

    • You can choose not to install X. Seriously, just don't install the X packages. However, most newbies want to use X because it provides an environment that is similar to what they are used to.
    • I don't really use Red Hat's hardware utilities, except Xconfigurator. Thus, I don't really have enough information to discuss this point.
    • I would argue that Red Hat pushes the rest of the distributions forward. Yes, there were quite a few bugs that were introduced with Red Hat 6.0. However, Red Hat released bug fixes and security updates. For 6.0, there are located here [redhat.com]; in fact, their entire support area [redhat.com] is pretty well done. And why should a company update old versions of its distro when it has already released a new one? I think that providing RPMs for support is quite sufficient. It's not a "service pack," but RPMs are really easy to use, and gnorpm is improving. It wouldn't surprise me to see a wizard-type interface be built on top of rpmlib through gnorpm.

    I'm all for allowing fresh faces to come use Linux. And if they want to use wizards, that's fine, too. I think that most 31337 Linux users feel the same way, as long as their methods of unbreaking things are still available.
  • by Devil Ducky ( 48672 ) <slashdot@devilducky.org> on Monday July 31, 2000 @04:11AM (#892458) Homepage
    How could it not "stay true to the look and feel of Unix"? Red Hat does not remove your ability to hack your system from the command line any more than Slakware does.

    It does however provide simpler tools to do it. I learned how to use linux on Red Hat. I used the tools to do what I didn't yet know how to, and I used the command line to do whatr i had already learned as I learned more I used the Red Hat tools less and less until I finally switched distros (Red Hat won't miss me I never paid them for it anyway). If I couldn't do it that way, I (and many others) would still be using, god-forbid, Windows.

    And if more people start using linux with Red Hat, well that just makes me happier.

    Devil Ducky
  • I've actually had a look at that before - but since I couldn't find any license in there, we can't ship any of them.
    Who can guarantee that the fonts we pick aren't taken from some company that will sue us for stealing?
  • by 11223 ( 201561 ) on Monday July 31, 2000 @04:15AM (#892463)
    RH is very leery about new sendmail releases until they've been thuroughly tested. kernel 2.4 is still very unstable; and they probably don't expect a stable patch to 2.4.0 to be out when 7.0 is released.

    Tux is still being worked on. Apache is probably being held for Tux.

    They've been burned by bind once already.

    Staroffice will be Open Source in October. It's not open source yet.

    Which LVM tool?

  • Probably the same inbred clueless moderator that marked it as over rated.
    Probably marked it as a troll because of the comments at the very beginning.

    Probably marked it as over-rated because (s)he didn't want to get marked down in meta-moderation. Although I haven't looked hard for it, this is probably a copy-and-paste, and the proper moderation could be argued to be "Redundant". (Probably afraid of "inbred clueless meta-moderators".)

    Anyway, the metalab link was wrong. It can actually be found at htt p://metalab.unc.edu/pub/Linux/distributions/redhat /redhat-7.0beta/pinstripe/ [unc.edu].

    --

  • I truly do not understand the purpose of releasing commercial beta code unless... Unless they want to use all their users to do their work for 'm

    No matter how large a company is, it can't possibly have all combinations of hardware, so how are we supposed to find bugs that occur only in systems that have the MyNet 2000 network card in combination with a Weirdo UW-SCSI card?
    That's (part of) why public betas are absolutely needed.

    As for supplying beta testers with the final version, I'm all for it (no, I don't have any say on this), but it's probably hard to do - how do you determine who did "enough" testing? 10 Entries in Bugzilla? Then what about someone who found only one bug, but submitted a perfect fix?
    You'll probably always end up being unfair to someone.
  • I presume that's a carefully selected snapshot

    For the beta, yes.
    Everything in there except for the kernel and some compat packages has been compiled with the snapshot.

    For the final, we hope to include the final release.

    Has the ia32 c++ ABI been finalised (and implemented)?

    Implemented: yes.
    Finalised: Hopefully, but there might be some more changes (which will of course make it into the 7.0 final).
  • I bet RH really really wanted to put XF86 4.0 and kernel 2.4 into 7.0. Can you imagine the problems if the kernel release schedule was dictated by RH (or any company)? They would be shipping 2.4.0-test3 (or whatever test we are at now)--with all the problems that implies. Long Live Open Source!
    --
  • by bero-rh ( 98815 ) <bero@reCOMMAdhat.com minus punct> on Monday July 31, 2000 @04:19AM (#892480) Homepage
    We're compiling some selected packages with optimizations - that way, we can still run on a 386, but get most of the speed out of optimizations.

    Also, since we're using gcc 2.96, the generated 386 code is probably somewhat faster than the "optimized" code earlier versions produced.
  • I apologize, this is not a flame, but there are a few things you missed. StarOffice will not be open source until october from what I understand. Redhat has never been in the practice of putting beta kernels in their distros, nor any other beta things for that matter. Mandrake, on the other hand, is known for this ;)

    And don't get me wrong. I would love to see all of these features, but often redhat does not go that cutting edge
  • Unfortunately the Adaptec AIC7xxx SCSI driver was REALLY broken and 6.2 won't even install

    It is my understanding that some cards using the AIC7xxx chipset are really broken and 6.2 doesn't have the right workarounds (it definitely works on my home machine with an original Adaptec 2940).

    Did you try the patch from http://people.redhat.com/dledford/ai c7xxx.html [redhat.com]? A couple of people have reported that fixes the problem (use the driver at the BOTTOM of the list), so I guess it's actually resolved.

    I don't have the actual hardware to verify this myself.
  • That's why distro inflate their numbers. Unfortuantly the commerical market thinks that higher numbers means much newer (and better). Its the very reason that Slackware jumped from 4.0 to 7.0 (they've openly admitted this). Just like your comment about Caldera, they didn't want people to say "Redhat 6.0 MUST be better than Slackware 4.1." Even Perl is doing it. Instead of making 5.006 they are going to 5.6, because people don't realize the significant change from x.005 to x.006

    ---
  • I agree with most all of your points. I have long thought that Linux was too "unstable".

    I feel that Microsoft Windows NT is too "unstable" and it only changes major components once a year.

    Major releases generally cause stress amongst IT shops, both trying to deploy upgrades as well as retest and develop software against the new changes. Ye olde Mainframe went for years without major changes, allowing IT to focus on solutions to problems rather than upgrades.

    Now I have to correct your FUD...

    Windows 98 is #2 in terms of retail sales of business software, at least according to www.pcdata.com. It's in the top 10 of all retail software sales.

    Windows Me is supposed to ship this fall, not two years from now, more like two months...

    RedHat 6.2 is #17 in business retail sales.

    Windows 2000 is #18 on the retail sales charts.

    As far as noone likes Windows 2000... That's not true. Personally my trials at home show it to be great. It's slow in sales right now only because corporations are slow to upgrade, due to the difficulties I pointed out above.

    Also given that most sales of Windows are in the corporate and OEM markets, it's not doing bad at all...
  • I was talking to someone who hires support staff, and he actually considers such certifications on a resume to be black marks.

    So in some cases, those certifications hurt your chances of getting a job.
  • by bero-rh ( 98815 ) <bero@reCOMMAdhat.com minus punct> on Monday July 31, 2000 @04:22AM (#892496) Homepage
    Each time the version number of glibc is increased by 0.0.1, Red Hat grabs the new version and uses it to bounce up its version number by 1.0

    Entirely untrue.
    We increase the major version number when there are changes that will prevent stuff compiled on the new version to run on the old version without being recompiled.
    For 7.0, that's caused by the change of compilers (C++ binary incompatibility) and glibc (2.2, not 2.1.8).
  • by bero-rh ( 98815 ) <bero@reCOMMAdhat.com minus punct> on Monday July 31, 2000 @05:16AM (#892500) Homepage
    What's missing:
    sendmail 8.11


    Missing from the beta, present in our current tree (and definitely the final).

    kernel 2.4test5ac

    Actually it's there, on the 2nd CD and not installed by default because it's known to have some critical bugs.

    tux 1.0

    Needs kernel 2.4

    apache 2.0pre4

    Chances are 2.0 won't be released in time for 7.0. It'll probably be in 7.1 (and I'll make RPMs for 7.0 available as soon as I have the time).

    bind 9.0

    Same as for apache - I'm actually using the 9.0.0 release candidate to host bero.org, but it has a couple of problems, like some missing utilities, and requires all master zones to be changed because the TTL stuff is now mandatory (and most people haven't used it with bind 8), so there's no really clean update path. Not something we could do in the couple of days between the 9.0.0rc1 release and the beta.

    staroffice

    It's still binary-only, they've just announced they'll GPL it by October 13th. We'll include it once that happened, until then, it will be on the Linux Applications CD in the boxed sets.

    LVM

    It's present in the 2.4 kernel we're shipping.

    reiserfs

    Too unstable at the moment. They keep changing the journal format, and the recovery tools aren't quite where they should be.
    Yes, reiserfs is nice while it works (I'm actually using it on one of my machines), but if something doesn't work and a journal replay doesn't fix it, you're usually in trouble.

    I'll make a kernel RPM with the patch available over at people.redhat.com/bero/experimental when I have the time (probably shortly after the 7.0 release) for those who want to play - but for now, we don't feel we can support it.
  • Red Hat Beta 6.0, 6.1 and Alpha 6.2 which include the newest and most unstable of all releases.

    You must be using a different 6.2 than the rest of the world then...
    If you have any issues with 6.2, report them [redhat.com] - we can't fix problems we aren't aware of. Considering my web server (running 6.2) has had an uptime of 103 days before I rebooted it for a kernel upgrade, I'd hardly call it alpha-quality code.
  • With almost all distributions (including Red Hat), most drivers are built as modules. Because you often need those drivers at boot time, Red Hat puts the modules you need into a ram disk image that gets used before your root partition is mounted. Personally, I like to rebuild my kernel with all critical drivers built in so as to avoid this ram disk.

    So how do you find out what drivers you need?

    Well, to start, use the command `lsmod` to see which modules are loaded. That should tell you which network driver you need to build.
  • It seems that they have gotton ride of bash 1.0 finally. 6.2 has this for install or something, but 7.0 beta does not. It also looks like they have some hybred XFree 3.3.6 -4.0 or something as there are rpms of both. They are still running apache 1.3 instead of 2.0 isn't apache2.0 out? They are running gimp 1.1.24 which I thought was beta. They do have gcc 2.96 and thins includes a java compiler for those of you who want to do java, hmmm. Gnome 1.2 which is cool. gtk 1.2.8 and 1.3. kde 1.91 hmm isn't this also beta? kernel 2.2.16.. hmm. Netscape 4.74 hmm what's that about. lots of updated libs. My Q is when will they update Tcl/Tk.. oh they have :-) 8.3.1. Cool they are including sane in there distro rather than the power tools .. sweet. New sawfish .. php 4.0.1. Hmm maybe it's time to get the srpms and recompile some of this on 6.2 instead of upgrading the whole system... Personally I wish they ship the stable stuff and then as an option on the install they could add the beta stuff like gimp 1.1.24. I don't think that everyone wants to be beta testers, they got enough of that with window 95. Yes some people do like being cuttinog edge, but the average users wants a system that works. Maybe this is an attempt at boosting there support. (ouch did I say that:-O)

    send flames > /dev/null

  • Why does there need to the start of beta? Should not all distributions be continuously in beta?

    Yes. And we are. Check out Raw Hide [redhat.com], which is actually a snapshot of our current development work, updated every couple of days.

    Our official betas are when we decide something has all the features we need in the final version, and generate ISO images to make it available to a broader group of people.
  • I have been keeping up with RawHide and I haven't seen anything going which would warrant a 7.0 designation

    All the major number increase means is that an application compiled on a 7.0 system won't run on a 6.x system without being recompiled (because of the glibc and compiler upgrades).

    Binary compatibility throughout a major number release is very important to us (do you think we LIKED keeping egcs 1.1.2 as the primary compiler in 6.2?).
  • Note that most fonts at Fontasti come in a zip that includes a readme file.

    Check the readme files - many of the fonts are free. Others include unclear license but have author address - you can send a query to the author.

    The problem with free truetype fonts, the way I see it, is not lack of fonts, but lack of good high-quality fonts for normal use.

    The vast majority of free fonts are fancy fonts that are not suitable as default fonts. Is there a possibility to create "Times New Roman", Helvetica etc? Are the fonts themselves copywrited, or only their manifestation as computer vector fonts?
  • Why does a multi-million dollar software firm seem to have no idea about major/minor software versioning? A quick pass over the binary packages included in this release tells me that the only major changes here are XFree 4 and gnome 1.2. For this we're going to version 7.0? Shouldn't this 7.0 release have included KDE 2 (not beta) and kernel 2.4 (not beta) at least to make it a new major version?
  • Does the XFree 4.0.1 in RH 7.0b come with it's own free TT fonts? (Freetype IIRC)

    Freetype is a LIBRARY that supports handling truetype fonts.
    We've been including it and patching XFree86 to handle it since 6.0 or so.

    However, there are no TT fonts included ATM (neither with the 7.0beta nor with Freetype) - if you can point me to a place that has good and free TT fonts that we could include, do.
    It's hard to find any high-quality free TT fonts.
  • with each major kernel release, a relatively major reconfig was required of certain packages to get optimal performance

    We're ready for 2.4 in these terms.
    Everything in the distribution has been compiled with 2.4 kernel includes, and all packages have been updated (we're even including iptables, the ipchains replacement for 2.4 kernels).

    why not include the beta kernel with a product not expected to ship for another few months?

    We don't expect to see a 100% stable 2.4.x release before going gold on 7.0. Therefore, we need beta testers to check how well our updates to the 2.2 kernels work with all sorts of hardware. That's why we're including the kernel that's closer to the default kernel for 7.0 final.

    If you take a look at the kernel source RPM, you'll see we've added a number of patches, such as USB support - we don't want to include them in 7.0 without having had any public beta testing on that kernel.

    Why rush 7.0

    I'd rather delay 7.0 by a few more weeks to wait for some projects, but it's out of the question for the business side.

    Not many would run beta in a mission critical situation

    Right - but the beta is supposed to be as close as possible to the final, and the final will have 2.2.17 by default (with 2.4.0 included on the CD for those who want to play).
    We can't go "2.2.17 is tested well enough, we'll just throw it in if 2.4.0test9pre7 isn't stable enough at release time" because we don't want to ship untested kernel patches. That would be suicide... (Then again, maybe not, seems like Microsoft has done it all the time :>)
  • by noa ( 4909 ) on Monday July 31, 2000 @04:37AM (#892537) Homepage
    I can not understand why redhat doesn't include any of the two available free (speech) SECSH (ssh2) implementations in their standard distribution. This would be a very simple step towards a much more secure out-of-the-box product. The crypto-regulations in the US shouldnt be a problem since OpenSSH and others are distributed by default.
  • by MartinG ( 52587 ) on Monday July 31, 2000 @05:30AM (#892538) Homepage Journal
    Oh come on, we can all see straight through that!

    We all know the REAL reason you release so often is because is gets announced on slashdot and you write replies to everyones comments. Your replies all get modded up to +5 and your karma soars.

    THAT is why RH really releases so often - You simply want more karma. :-)

  • Well, I think Slashdot should HOLD OFF posting release announcements until it's posted on the companies or project web site. I know I know it's been said before, but both today's KDE Beta 3 and Red Hat's beta of 7.0 have been posted BEFORE it's officially linked from the top page of the site(Red Hat never links this stuff to the top, but KDE always does). It's putting loads on the servers before the stuff is there sometimes! Mirrors can take a while to get their updates. This is not fair to the people who are trying to get something else off of the server beside the release. Since the mirrors don't all have the files yet, the main site get's /.'d. I think Slashdot should chill on the release announcement until the announcement appears, or until the mirror's are all updated. All of the people who really want it, get it anyway whether it's on /. or not.

  • It would seem readily apparent that some postings here are only present to start pissing contests. Hopefully this is not one of them.

    Please stop arguing about which distro is better. Any Open-Source OS that can be tuned to YOUR needs is the one you should use. It's not about which one, its about all of them.

    It's getting boring to read _lame_skript_kiddie_ complaints about how *pick-your-distro* doesn't have a 2.4 kernel, or StarOffice, or whatever. Did you know you could go get it yourself, review the code, configure, make, and install too?

    If you didn't like it, you can change it, yep, learn a little programming, and make it exactly how you want it .. now how much would you pay ? All the distros have that built in.

    Can you do that with MS ? nope nope nope, You get it Bill's way.

    Anyways ...

    So Beta 7 is out, great, RH is taking a positive step towards decreasing the MS marketshare on the desktop. I think that a 6 month turnaround is about right, remember, MS released new OS's what, about every 3 years (95->98, 3.51->4.0->2000). That is one of the benefits which is driving *nix up the marketshare ladder, server and desktop.

    Lets pull it apart boys !!! (and girls)

    -BrewX

  • It's not about crypto regulations this time, it's about the #include <favorite-curse.h> RSA patent.

    [Open]SSH uses RSA for host key authentication.

    We've made RPMs available at ftp://ftp.redhat.de/pub/rh-addons/secur ity/ [redhat.de], where the RSA patent doesn't apply, though.

    AFAIK you may not use them in a place where the RSA patent applies, so don't get them unless you're outside of the US and any other contry that has the RSA patent.

    Fortunately, the patent will expire later this year.
  • Not for now, because it's too unstable (journal format changing every couple of releases), and once you've managed to mess up a filesystem beyond what a journal replay can fix, chances are you're in trouble with reiserfs.
    Once it has stabilized, we'll include it unless something better comes along before that.

    For 7.0, I'll put up a kernel RPM with the ReiserFS patch on http://people.redhat.com/bero/experimen tal/ [redhat.com] when I have the time (probably shortly after the 7.0 release) for those who want to play, but don't say I didn't warn you.
  • I don't really like that it boots to X as default

    You can turn that of at installation time if you choose a custom install.

    The reasoning is, basically, that someone who can't run a custom install probably won't find his way around on the text console. Someone who can (and wants to) handle the text console as primary UI is much more likely to know how to vi /etc/inittab than someone who is just looking for a way to start an easy interface at bootup.

    I didn't mean to be insulting of course

    I thought so - I just prefer "an advanced user might miss the XYZ feature FreeBSD has" over "it seems to be targeted more at newbies", because once we know WHAT is missing, we can fix it...
  • Both are right actually - the main dist consists of the two CDs, but for a normal installation, the first will suffice.
  • I think it's cool that the Red Hat folks take the time in their busy schedule to come here, in Slashdot, to keep us informed -- right from the true source.

    People who say that RH have sold out are plain wrong.
  • Oops, you caught us... :)
    Yes, the plans are to get a user account with karma > whatever the code currently supports, thereby causing a buffer overrun and taking over Slashdot, and thereby WORLD DOMINATION!

    Oops, now I told too much.

    Guess I'd better do something to make at least some people believe we're releasing because we're actually improving something...

    400th post!

    I'm currently pouring hot grits down my pants and looking at a Natalie Portman poster!

    Your favorite Linux distribution sucks, all real people do "cat >/dev/hda"!

    Hope this qualifies as Troll, -1. ;)

    Obviously, I'm not after Karma.
  • Here's how to configure & build a stock RedHat kernel. This won't work when you upgrade to a new kernel, but at least you can look at all the options as they are configured.

    Look in /usr/src/linux/configs

    You'll see several files, names something like
    kernel-2.2.15-i386-BOOT.config kernel-2.2.15-i586.config
    kernel-2.2.15-i386-smp.config kernel-2.2.15-i686-smp.config
    kernel-2.2.15-i386.config kernel-2.2.15-i686.config
    kernel-2.2.15-i586-smp.config

    Decide which one you want. I'm using
    kernel-2.2.15-i386.config on my laptop and
    kernel-2.2.15-i686-smp.config on my desktop.

    You that you have a file, in /usr/src/linux, run
    # make xconfig
    or
    # make menuconfig
    Depending on X or Text mode. Look for an option like "Load Alternative Config File". Type/Paste in the name of the file you picked. Save & Exit.

    # make dep; make clean; make; make modules; make bzlilo; make modules_install
  • It's Linux 7.0 that's out. See, all my favorite commercial apps say they require "Linux 6.2" to run, so therefore this latest version must be Linux 7.0. And we all know the commercial programs must be right because they can afford to sell the products. If this GNOME thing was any good, they would sell that too.

    BTW, what's this "kernel" thing people keep talking about?

    (hey mods, it's a joke)
    --
  • According to Caldera [calderasystems.com], they have released their Developer Preview of Linux Technology which is described:

    Caldera's Linux 2.4 Technology Preview includes:

    • Preview of Linux 2.4 kernel technology
    • Beta preview of Java 2 platform for Linux, version 1.3
    • Java HotSpot Client and Server Virtual Machines
    • glibc 2.1.91: (2.2 beta)
    • Latest C/C++ Linux development tools
    • KDE 2.0 Development Snapshot
    • Improved USB support
    • PHP3 and PHP4 for rapid development of dynamic Web sites

    This is not to be confused with Caldera's confusing versioning scheme in which 2.2, 2.3 and 2.4 all were based on Linux kernel 2.2.x. Maybe Caldera will jump up to 7.0 when the real 2.4.0-honest-to-God comes out in October 200x, and RedHat, Mandrake, Slackware, and SuSE all come out with 8.0.

  • The contest of being to first to announce a distro has a beta out. Pissing contest for geeks. Have to love it. I do wonder, though, how much wasted bandwidth goes to ftp lurkers waiting to pounce at the first sign of something beta.

    Bryan R.
  • Bero - it's not about patching the kernel - everyone can patch the kernel easily...

    Its about installation. Mandrake 7.1 gives you the ability to create a ReiserFS and a swap partitions - and thats it! you don't need another ext2 partition for booting etc.. - and THATS the beauty here..

    So, what about releasing a boot/root disk that will add the options to create a ReiserFS in addition of ext2? like Mandrake does...
  • what are the problems with 6.1? I've been using 6.1 for over 6 months (since shortly after it came out) without encountering anything serious (other than the bind vulnerability). Mind you, I've replaced the kernel and modified several other things.
  • by Booker ( 6173 ) on Monday July 31, 2000 @05:46AM (#892579) Homepage
    Red Hat is doing some cool things on the business side of things, but they really need to stay focused on the details... why does their mailing list page [redhat.com] only have archives up to 2/2000? And why aren't some of the lists they host (like video4linux) archived at all?

    It's little things like that that can really irk your support base... the pointy hairs might not notice, but we do.

    ---

  • Well, I've been using Linux for four years now, and I still use Red Hat - on my servers and on my desktops.

    I started on Slack in 1996. Painful. But I loved it. Today I know and understand linux, and I'm looking at being more productive. Sure you can use cp and mv and find -name, but that gets tedious and redundant. Nothing beats the ease of point-and-click. I recently installed Slack 7.0. Downloaded the ISO. Still had to make those root/boot disks. Sorry to say, but Bootable CD's aren't just for newbies.

    The RPM is (IMO) the best package manager out there. Upgrades are easy, new software installs are easy. Don't get me wrong, I love compiling software as much as the other dude, but that's not productive for _me_. Give me a binary RPM so I can _use_ the stuff. The .tgz's of Slackware are just non-standardized enough, and that's why no software maker will claim it works on Slack.
  • by egon ( 29680 )
    Looking in the iso directory:

    pinstripe-en-i386-cd1.iso
    pinstripe-en-i386-cd2.iso

    Are they finally breaking down and needing 2 CD's?
  • haha. oh, yeah. but we're still behind Solaris 8 :)

    javajawa# sleep
  • by tmu ( 107089 ) <todd-slashdot@renesys . c om> on Monday July 31, 2000 @03:11AM (#892611) Homepage
    I haven't installed it yet, but it looks as thought the Logical Volume Manager tools still aren't packaged with the distro. This concerns me. This is among several concerns I have about RedHat's future directions. I've always liked redhat (since the Mother's Day release back in the day) and especially have appreciated their attempt to balance the new and fancy with stability and security.

    But recently they've been failing on both fronts. Suse seems to be taking the lead on new features (with their support of X drivers, and shipping LVM and reiserfs), and Redhat has slipped on the security front. Redhat took two weeks (two weeks!) to issue patches the the last round of security problems affecting the 2.2.14 kernel. Not the 24-hour turnaround I've come to expect.

    I suspect the distro will be good in other respects, though.
  • by oingoboingo ( 179159 ) on Monday July 31, 2000 @03:13AM (#892612)
    less and less to those who seek to immerse themselves in the goodness of a unix environment (bad).

    how does RedHat (or any distributon, for that matter) lessen the potential for total immersion in the unix environment? it's not like the graphical admin tools and scripts that are provided mean that you can no longer go into /etc with vi and hack till your heart's content.

    skip automatic hardware detection, don't set up TCP/IP at install time, don't install any windows managers, and certainly don't install GNOME or KDE. there you go...its thin'n'crispy (tm) just like unix 'should be'.

    on the other hand, you can install all the bells and whistles if you'd like, and pretend the technical details don't exist

    i thought this whole 'choice' thing was what linux was about?
  • Making less releases would put us behind all the others (just imagine the slashdot announcement "SomeDistro 10.3 released, has Kernel 2.4.1 and KDE 2.0, while Red Hat is still at Kernel 2.0.38 and KDE 1.0" - nobody (except for some Red Hat haters, maybe) would like that!) - at the pace of development in inux, 6 months can be a major change...

    Uhm, actually, as a Debian user, I'm pretty much used to this situation.

    Except of course that we don't even have KDE 1.x yet... (c:

    (of course, I still *use* Debian...)p.--Cycon

  • The version number looks like a marketing trick to me...

    If you take a look at what have been changed from RH 6.2 -> 7.0 - you'll see that its not much...

    So my guess will be that it will take you from 1 day to 1 week to learn what has been changed and study the changes...

    I'm sure that no one will disqualify you because you have the RHCE for 6.2 while they'll use 7.0 :)
  • by Dan Hayes ( 212400 ) on Monday July 31, 2000 @03:14AM (#892624)

    Well, this is great news for the community since like it or not, public perception of Linux comes from what RedHat are doing more than any other organisation - hence this'll be seen as Linux 7.0, which sounds better to the newbie than Linux 2.4.0-test3 :)

    It does seem that people who are long-term Linux users don't use RedHat anymore, maybe because it has been geared towards the "newbie", but at the end of the day surely Linux is Linux, and you can set up any distribution how you like given a bit of time.

    Still Linux does need something aimed at helping newer users overcome the initial "fear factor" of running Linux. Whether you like it or not, by doing so they're doing everyone a favour in the long run. So although I don't use it, I wish them all the best and hope this release goes well for them.

  • Well, according to the dates that the KDE team posted, KDE 2.0 will be out the door before RH 7.0 will be released as gold.

    Take a look at the releases of KDE beta's and you'll notice that they were released exactly as planned (with few days more for packaging - but I'm sure this is not a problem for Redhat).

  • In band meta-discusion is not only unacceptable, it should be cause for immediate dekarmaization.

    Bah! Wait, lemme say that again... Bah!

    I couldn't give a shit about the karma, I've got karma to burn. But the "unacceptable" bit bugs me. So much so, in fact, that I'm doing it again.

    DON'T MAKE ME LOAD THIS THREAD AGAIN! I'LL GET OUT THE BELT!
  • I predict 15 red hat vulnerabilities will be posted on securityfocus within 48 hours. at least the script kiddies will be kept busy scanning ip addresses for boxes running the beta distribution and wont bother with trying to crack my freebsd box.
  • RedHat's basic OS strategy seems to be to release a .0 with lots of new stuff and improvements, but with it inevitably comes lots of bugs. For example 6.0 had 2.2 kernel, libc6, etc. the first distribution to do that. But it was terrible, lots of problems and bugs that I have seen on many 6.0 systems, like the mysterious "Shutting down X font server [FAILED]" and "nfsd: terminating on signal 9" messages every time to halt/reboot. The version of GNOME it came with was also really unstable.

    Then RedHat fixes most of these problems in a .1 release. I was much happier with 6.1 when I quickly installed it. It worked much better but I didn't appreciate the unmaintained/undocumented text mode installer, or the fact it didn't install a kernel with kernel module loader.

    I don't know about the .2 releases, but I presume they fix more problems, making them the most stable.

    So imaging what a beta of an unstable product will be... 2.4.0-test4pre2, gcc-3.0pre5, etc.
    I would stick with 6.2 unless you're really brave.
  • by LordNimon ( 85072 ) on Monday July 31, 2000 @05:59AM (#892637)
    Here's a feature I'd like to see in 7.0:

    It would be great if the installation routine could create a .config file in /usr/src/linux that would match the current installation and hardware! I can't build a new kernel because I can't figure out what network card I have (/proc/pci says one thing, conf.modules says something completely different, I can't find the chip on the motherboard, and nothing I've tried works anyway). However, the installation itself knows what hardware I have, but if I try to build another kernel, I have to manually figure it all out. There is no reason for this.

    The installation routine should generate a .config based on the hardware it has detected and the options the user chose during the installation. In other words, I should be able to build the kernel from /usr/src/linux without specifying any options, and it should work!
    --

  • Fonts are copyrighted as computer programs. The glyph shapes themselves are uncopyrightable (the longest English word that doesn't repeat a letter).
    <O
    ( \
    XGNOME vs. KDE: the game! [8m.com]
  • I think (danger, I am going from memory here), you can type "make oldconfig" and it will restore the default previously built settings. I ran across this in some red hat kernel building documentation while I was trying to get my wireless ethernet cards working.

    This will not solve all your problems mentioned, but it is a good step in that direction.

    Bill
  • Will there ever be a mta other than sendmail? I'd like qmail included.
  • Moby Dick bites my ass. I don't need 2 chapters on chowder and 3 on harpoons.
    I gotta agree there. However, Shakespear, now that is literature.
    To troll or not to troll, that is the question
    wether tis nobler in the mind to suffer the slings and arrows of moderation, or to login to a sea of troubles, and by posting intelligently gaining karma
    To whore, to troll, no more
    And by a troll we say to end
    The intelligence and thousand on-topic threads that slashdot was heir to.
  • I certainly agree that there can be some significant irritations come out of having releases come so often.

    It is nonetheless not at all obvious that this winds up causing an actual problem.

    After all, if a new version comes out every 6 months, that means that CompUSA and BestBuy have the opportunity to have regular displays that say: New! Improved! Buy now!

    I would certainly agree that this results in there being some obsolete RHAT boxes out there that may become virtually unsalable. That does not forcibly represent a problem; computer stores have already needed to be able to cope with "best before" dates, and dealing with products that have to head to the Bargain Bin.

    Thus, for Red Hat Linux releases to exercise the "Bargain Bin" does not forcibly represent a problem for retail marketing.

  • Yes, the money that comes in from such will suck. It is a bit more likely that the old 6.x boxes get sent back to RHAT in exchange for new 7.x boxes.

    The point really is that there are mechanisms already in place for coping with returns, and a fair bit of control is in the hands of retailers, at least those that buy in bulk.

    If BestBuy knows that RHAT does a release roughly every five or six months, but winds up over-ordering based on estimating sales badly, I'm not sure why this ought to be considered the fault of RHAT. The dummies are in BestBuy's purchasing department...

  • Looking at the features, I dont see why this would be a 7.0 release. The only real major upgrade is XFree86... I think they should release this as 6.3, and when Gnome2, KDE2, Kernel2.4, etc is out, and stable, then make it a 7.0 release.
    -Brandon
  • XFree86 4.0.1
    Latest Beta KDE (3!)
    MySQL Now Included
    Latest Postgres

    Looks like some fun stuff. Intesting that they wouldn't include a beta of the kernel but of KDE. Guess RedHat knows what will and will not be done by the time 7 ships.

    Bryan R.
  • by Jeremy Erwin ( 2054 ) on Monday July 31, 2000 @06:10AM (#892663) Journal
    The latest kernel is 2.40.pre5 (It's upgrade time for me.)

    I was looking at Redhat-beta-pinstripe on sourceforge, and they do have SRPMS for
    XFree86-4.0.1
    kernel-2.2.16-17
    and
    kernel24-2.4.0-0.16

    So their hopes must be pretty high. I bet the final release of 7.0 will have kernel 2.4.1, at least as an option. The big selling point will probably be the GLX support for the i810, rage128, matrox, voodoo3, etc.

    They do have support for Xfree86-3.3.6, though, so they may be hedging their bets.
  • If all your hardware is detected why do you need to rebuild your kernel? Rebuilding a kernel on modern hardware should only be required if you add hardware that the kernel does not know about. Personally I think that all drivers shoudl be built as modules and then noone neds to build a new kernel, unless they upgrade.

    send flames > /dev/null

  • I also am finishing college in a CS program in only 3 years, and I could have done it in 2 except...

    ...that I spend way too much time posting on Slashdot.

    --

  • We're down to 30 or so packages in a minimal install.

    Excellent. I tried to install RH6.2 onto an LS-120 to use as an emergency boot disk, but it didn't fit. When your base install, with no packages selected is over 120MB, it's a sure sign you've gone too far in the bloat direction. Then again, I've been using Linux since it came on a boot and root disk direct from Linus, so everything seems a bit bloated these days :-)

  • I take a different approach. Install a base development system and a compiler. Build gcc from source. Uninstall everything but the barebones; cut deep. Build everything you want - kernel first, then libs, then apps - from clean sources. It's a lot more up to date, and I don't have to worry about what kind of funky patches Red Hat was smoking. Naturally this begs the question; why not just build my own distro, or use a different one? One word: kickstart. It's far, far easier to kickstart 40 workstations from the same barebones setup and NFS mount a full system on them than it is to maintain the same 40 workstations with any other setup.

    To other distro maintainers: when you can duplicate the effects of kickstart (or roboinst or jumpstart, etc), I'll use your distro. I hate Red Hat, but you're just not getting the job done for me. Sorry.

  • by Lumpy ( 12016 ) on Monday July 31, 2000 @03:22AM (#892685) Homepage
    Let's see, most comp-usa's and other retailers that are nervous about selling linux to begin with are going to be stuck with shelves full of 6.2 releases when the 7.0 release comes out ov beta in 30-60 days... Man, if I was a retailer I would really think twice about stocking RedHat on my shelves. First it's not selling as fast as the other (OK Win isn't selling either but 98 is still a current release... millenium isnt expected for another 24 months, and noone likes 2000) so here's this upstart that makes me eat 20 copies of their software every 3 months. Example : I start with 6.0 - 6.1 comes out then 6.2 and now 7.0 beta means 7.0 final is soon. this is all within the past 12 months... As a store manager, I would have to make a decision to not carry redhat on my shelves as it is too "unstable"

    I fear that RedHat will drive the penguin out of the retail market faster than any MS generated FUD could .

  • About twenty minutes after the beta directories were opened up on the mirrors, the first of the ERRATA files were transmitted to the mirrors for downloading...
    FNORD!

  • by Jon Shaft ( 208648 ) on Monday July 31, 2000 @03:27AM (#892694) Homepage Journal
    Debian has the *RIGHT* version number sequenece. All this distribution hoping up to 7 is ridiculous.

    Picture things in 2 years, we're going to have Redhat Version 14, Slackware Version 15.1, and SuSE 42.

    They're going to have to stop the insanity eventually! :)

  • I make it a point to always buy the newest version of Red Hat, just to support my fav company, but occasionally, I have to wait for the store I get it from to get more in, because they say they sell Red Hat's stuff very quickly. To quote the guy at the cash register, "Yeah, I may wanna try it, people seem to be buying it a lot these days." Sure it could sit up and take up shelf space, but I see a lot of places selling it rather easily. Don't even ask me how long the local Media Play managed to keep their hands on 12 copies of Corel Office 2K for Linux....ahem gone in a week....
  • I'm running reiserfs with journaling on 2.2.13. That works fine (so fine that I've moved everything except root,home,archive partitions on my machine over to it). That said, reiserfs with journaling on 2.4.0test does NOT read them (i.e. refuses to mount).

    This is a problem that I have, and is probably one that THEY know of, and is a good reason not to include reiserfs as part of the basic install.

    Including the reiserfs patch (as part of an upgraded kernel source archive), and providing ext2-to-reiser utils (if and when they are written) would help things a good deal.

    p.s. I haven't bothered to check/contact the reiserfs mailing list over this. This is not an excuse for me not having the problem 'fixed' -- 2.2.13 works fine for me. However it is a valid excuse for not having reiserfs in -their- kernel at this point.

    p.p.s patience. I'd personally like to see LVM first, and reiserfs to wait in the wings until it is virtually (i.e. at least appears) designed for LVM.
    John
  • I'm currently running RedHat 6.1, but there are two things that have always struck me as attractive about Debian:

    (1) There's an apt-get mechanism that you can set up to do automated updates (think, security patches) of your system software. Redhat is working on this, too, but Debian has been there for a long time.

    (2) They don't ship alpha quality software! I sincerely hope that RedHat has bought some QA with their IPO money, because despite having a reputation for being easy to install, RedHat upgrades always strike me as a severe nightmare.

    (Hey, maybe I'll try a *beta* release of a "x.0" version of RedHat! That sounds so exciting! Uh, on second thought....)

  • Hmm... Then you just undid your moderation:-)
  • No bashing intended here but I truly do not understand the purpose of releasing commercial beta code unless... Unless they want to use all their users to do their work for 'm, to a certain extent at least. Don't get me wrong; I'm not claiming that this is a bad thing, I do find it odd. Especially if people go out and test the beta and finally will purchase the boxed set. The least RH could do is grant those users a small refund or another small gesture for their hard work.

    But then again; I also can't understand why people buy Microsoft beta's and participate in the testing. MS is afaik the only company which can test a beta and make money out of it as well.

  • FWIW, I just found out that the Pinstripe archives are at https://listman.redhat.com/pipermail/pinstripe-lis t/

    A few other lists are up, too - see https://listman.redhat.com/mailman/listinfo

    ---

  • You must means SunOS 5.5.8? Or is that Solaris 2.8? Too many #$@#$ version numbers...
  • Here is a short list
    • Kernel is a 2.2.17pre, with extra patches...
    • Xfree is 4.0, but XFree 3.3.6 servers are used on many cards
    • GNOME is 1.2
    • KDE is a KDE 2.0 shapshot. Urgh.
    • glibc is 2.2ish
    • compiler is 2.96ish
  • by avdp ( 22065 ) on Monday July 31, 2000 @03:50AM (#892752)
    That's just wonderful...
    I just got the RHCE certification (didn't really care about it but my company insisted on paying for it, so who am i to argue?). Since the certification is specifically for RH6.2, and that it will expire at the end of the RH7.x serie (that's what the instructor said anyway, but nobody is really sure) - at the rate RH is going that should be in a year or so?

    As I said, I am glad my company paid for this. Considering how much it cost ($700 just for the test), and how soon it becomes obsolete, I would NEVER have paid for it.
  • Nine times out of ten MS betas are far more stable than release versions. I'm quite convinced a vital step in the MS development process is "beta test to ensure optimum bug saturation - add bugs as necessary to taste". I think the point that was being made is that it isn't necessary to HIDE stuff; put up a link, let the morons who decide to download it and kill their systems die, it's their own problem.

    ---
    Tim Wilde
    Gimme 42 daemons!
  • &gt"Document roots for Apache and anonymous FTP are removed from /home so it may be automounted. "

    What the heck does that mean, exactly?


    Sun started (I think) the practice of the /home directory being a default automount point (meaning you access other people's remote home directory though /home). They use /export/home for the actual location of local home directories. Redhat used to place local things in /home, making it more difficult to use in a heterogenous environment.

    By taking everything out of /home, you can use it as an automount directory without RPM being upset when you upgrade Apache or FTP.

  • Oh, yes. Suggesting that people who can't browse an FTP site (or get links mailed to them on the announce list) probably shouldn't watch their system being torn into shreds by a beta distribution is going to ruin Linux's chances in the real world.

    So that's the reason my grandparents got Win2k betas?
  • We are aiming for better binaries - more ones, less zeros.

    Seriously speaking, we compile with optimizations for pentiumpro but no architecture specific commands (selected packages excepted, like glibc and the kernel). And since we use a compiler with a new x86 backend, we should actually see some performance gain - previously, "optimizing for pentium" with gcc was just a gimmick.

  • Announcing...

    Red Hat Linux "Pinstripe"
    a Beta release

    Red Hat. Inc. presents a beta release of Red Hat Linux for your
    hacking pleasure. First, the regular drill:

    This is a beta release of Red Hat Linux. It is not intended for
    mission critical applications. It's not even intended for
    non-mission critical applications. Important data should not be
    entrusted to Pinstripe, as it may eat it and make loud belching
    noises.

    Significant changes have been made since the last version of Red Hat
    Linux. We need your help to find and report bugs. Search for
    existing bug reports for problems you find by using bugzilla at:

    http://bugzilla.redhat.com/bugzilla/ [redhat.com]

    Attach patches if you're motivated!

    This beta includes so much cutting edge software, the binary packages
    come on two iso images. The installation program now handles reading
    packages from multiple CDs.

    * Where can I get this release?

    Pinstripe can be downloaded from our public FTP site at:

    ftp://ftp.redhat.com/pub/redhat/beta/pinstripe

    With the support of volunteers ftp site administrators, Pinstripe is
    available from several mirrors. The following have complete copies of
    Pinstripe, please use a mirror close to you:

    North Carolina, USA:
    ftp://metalab.unc.edu/pub/Linux/distributions/redh at/beta/pinstripe/
    http://metalab.unc.edu/pub/Linux/distributions/red hat/beta/pinstripe/

    California, USA:
    ftp://ftp.sourceforge.net/pub/mirrors/redhat/redha t/beta/pinstripe/
    http://ftp.sourceforge.net/pub/mirrors/redhat/redh at/beta/pinstripe/

    California, USA:
    ftp://ftp.kernel.org/pub/mirrors/redhat/redhat/bet a/pinstripe/
    http://www.kernel.org/pub/mirrors/redhat/redhat/be ta/pinstripe/

    Connecticut, USA:
    ftp://ftp.uselinux.org/pub/redhat/beta/pinstripe/

    Indiana, USA:
    ftp://csociety-ftp.ecn.purdue.edu/pub/redhat/beta/ pinstripe/
    http://csociety-ftp.ecn.purdue.edu/pub/redhat/beta /pinstripe/

    Michigan, USA:
    ftp://mrhankey.bizserve.com/pub/linux/redhat/ftp.r edhat.com/redhat/beta/pinstripe/

    New York, USA:
    ftp://ftp.ee.cornell.edu/pub/linux/redhat/beta/pin stripe

    Pennsylvania, USA:
    ftp://carroll.cac.psu.edu/pub/linux/distributions/ redhat/redhat/beta/pinstripe/

    Pennsylvania, USA:
    ftp://cronus.res.cmu.edu/pub/linux/ftp.redhat.com/ beta/pinstripe/

    Tennessee, USA:
    ftp://sunsite.utk.edu/pub/linux/redhat/redhat/beta /pinstripe/
    http://sunsite.utk.edu/ftp/pub/linux/redhat/redhat /beta/pinstripe/

    Australia:
    ftp://mirror.aarnet.edu.au/pub/redhat/beta/pinstri pe/
    http://mirror.aarnet.edu.au/pub/redhat/beta/pinstr ipe/

    Germany:
    ftp://ftp.gmd.de/mirrors/redhat.com/redhat/beta/pi nstripe/

    Germany:
    ftp://ftp.uni-bayreuth.de/pub/linux/redhat/beta/pi nstripe/
    http://ftp.uni-bayreuth.de/pub/linux/redhat/beta/p instripe/

    Norway:
    (ISO images only)
    ftp://carroll.cac.psu.edu/pub/linux/distributions/ redhat/redhat/beta/pinstripe/

    Peru:
    ftp://sajino.terra.com.pe/pub/linux/redhat/beta/pi nstripe/

    Japan:
    ftp://ftp.kddlabs.co.jp/Linux/packages/RedHat/redh at/beta/pinstripe/

    * What's new in this beta?

    General system improvements:
    o FHS compliant packaging of files
    /usr/man is now /usr/share/man
    /usr/doc is now /usr/share/doc
    /usr/info is now /usr/share/info
    See http://www.pathname.com/fhs/ for more information

    o Document roots for Apache and anonymous FTP are removed from
    /home so it may be automounted.

    o Packages with services are automatically restarted on live
    upgrades

    o Expanded LDAP integration

    o Expanded Kerberos integration

    Core system components:
    o glibc 2.1.91
    o XFree86 4.0.1, XFree86 4.0.1 runtime environment
    o XFree86 3.3.6 X servers included for maximum hardware compatibility
    o GNOME 1.2
    o kernel 2.2.16
    o GCC 2.96

    Expanded hardware support:
    o Basic USB support (mouse and keyboards)
    o Expanded hardware accelerated 3-D support

    System service changes:
    o inetd replaced by xinetd
    o BSD lpr replaced by LPRng

    A sampling of package upgrades:
    o GIMP 1.1.24
    o Perl 5.6.0
    o Tcl/Tk 8.3.1

    A sampling of Package additions:
    o SDL, smpeg
    o SANE
    o gphoto
    o MySQL
    o AbiWord
    o dia
    o ispell has been replaced by aspell
    o XEmacs

    Next generation development library previews included:
    o pango: Unicode font rendering
    See http://www.pango.org/
    o Inti: C++ foundation libraries including GTK+ GUI toolkit classes
    See http://sources.redhat.com/inti/

    Enjoy!

    The OS Development Team
    Red Hat, Inc.

  • by pyrotic ( 169450 ) on Monday July 31, 2000 @03:54AM (#892773) Homepage
    Here's what's new about RH 7.0:

    perl 5.60
    php 4.01 - speed boost over version 3
    mysql - now open source, no longer just in power tools
    XFree86 4.01 - speed boost over version 3
    enterprise kernel - raw filesystems and other performance patches
    kde 1.91 - beta for 2.0, includes new browser
    kde office 1.91

    And what's missing:

    sendmail 8.11 - crypto smtp
    kernel 2.4test5ac - decent smp performance
    tux 1.0 - very fast RedHat kernel web server
    apache 2.0pre4
    bind 9.0 - major rewrite
    staroffice - now it's open source
    LVM
    reiserfs


    Sendmail and staroffice aren't beta and should have gone into this release, the rest are probably too bleeding edge. Anyone think of anything I've missed?
  • I suspect that the guys who pay $70 (or whatever it really costs) for a Redhat distribution are not aware of the beta release schedule of 7.0.

    In other words, I think the guys who read /. are downloading their distributions.

    Vanguard

    PS Or, maybe I'm living in a DSL induced fantasy land?
  • by ponxx ( 193567 )
    SuSE has apparently decided to split their 7.0 distribution into a "personal" and a "professional" edition. According to their website they're going to release it on August 21. ( sorry, this is in German [www.suse.de]).

    Personal is aimed at the desktop-market, so maybe it will be preconfigured not to run all services under the sun by default and make beginners a bit less vulnerable.

  • Actually, they are moving to Gcc 2.95 (2.96?) and a newer glibc, which means they are breaking compatibility w/ 6.x releases (well, they may include old compatibility libraries, but it isn't a trivial change). Another 6.x release means they would probably have to keep using egcs-1.1.x.

    Kernel 2.4 is optional (and the release should be mostly compatible w/ 2.4 final)
  • So where will the FTP and HTTPD homes be now?
  • less and less to those who seek to immerse themselves in the goodness of a unix environment

    How so? (If we don't know what's wrong, we can't fix it!)
    I'm running it without X about 90% of the time, I'm not missing anything...
  • by Chyeburashka ( 122715 ) on Monday July 31, 2000 @03:58AM (#892789) Homepage
    From the redhat-announce email:

    With the support of volunteers ftp site administrators, Pinstripe is available from several mirrors. The following have complete copies of Pinstripe, please use a mirror close to you:

    North Carolina, USA:
    ftp://metalab. unc.edu/pub/Linux/distributions/redhat/beta/pinstr ipe/ [unc.edu]
    http://metala b.unc.edu/pub/Linux/distributions/redhat/beta/pins tripe/ [unc.edu]

    California, USA:
    ftp://ftp.sourc eforge.net/pub/mirrors/redhat/redhat/beta/pinstrip e/ [sourceforge.net]
    http://ftp.sou rceforge.net/pub/mirrors/redhat/redhat/beta/pinstr ipe/ [sourceforge.net]

    California, USA:
    ftp://ftp.kernel.org /pub/mirrors/redhat/redhat/beta/pinstripe/ [kernel.org]
    http://www.kernel.o rg/pub/mirrors/redhat/redhat/beta/pinstripe/ [kernel.org]

    Connecticut, USA:
    ftp://ftp.uselinux.org/pub/redhat /beta/pinstripe/ [uselinux.org]

    Indiana, USA:
    ftp://csociety-ftp.ecn .purdue.edu/pub/redhat/beta/pinstripe/ [purdue.edu]
    http://csociety-ftp.e cn.purdue.edu/pub/redhat/beta/pinstripe/ [purdue.edu]

    Michigan, USA: ftp://mrhankey.bizserve.com/pub/linux/redhat/ftp.r edhat.com/redhat/beta/pinstripe/ [bizserve.com]

    New York, USA: ftp://ftp.ee.cornell.edu/p ub/linux/redhat/beta/pinstripe [cornell.edu]

    Pennsylvania, USA: ftp ://carroll.cac.psu.edu/pub/linux/distributions/red hat/redhat/beta/pinstripe/ [psu.edu]

    Pennsylvania, USA: ftp://cronus.res. cmu.edu/pub/linux/ftp.redhat.com/beta/pinstripe/ [cmu.edu]

    Tennessee, USA: ftp://sunsite.utk.edu /pub/linux/redhat/redhat/beta/pinstripe/ [utk.edu]
    http://sunsite.u tk.edu/ftp/pub/linux/redhat/redhat/beta/pinstripe/ [utk.edu]

    Australia: ftp://mirror.aarnet.edu.au/pu b/redhat/beta/pinstripe/ [aarnet.edu.au]
    http://mirror.aarnet.edu.au/ pub/redhat/beta/pinstripe/ [aarnet.edu.au]

    Germany: ftp://ftp.gmd.de/mirrors /redhat.com/redhat/beta/pinstripe/ [ftp.gmd.de]

    Germany:
    ftp://ftp.uni-bayreuth.d e/pub/linux/redhat/beta/pinstripe/ [uni-bayreuth.de]
    http://ftp.uni-bayreuth .de/pub/linux/redhat/beta/pinstripe/ [uni-bayreuth.de]

    Norway: (ISO images only) ftp ://carroll.cac.psu.edu/pub/linux/distributions/red hat/redhat/beta/pinstripe/ [psu.edu]

    Peru: ftp://sajino.terra.com.p e/pub/linux/redhat/beta/pinstripe/ [terra.com.pe]

    Japan: ftp://ftp.kddl abs.co.jp/Linux/packages/RedHat/redhat/beta/pinstr ipe/ [kddlabs.co.jp]

  • by Nassah The Zerg! ( 16666 ) on Monday July 31, 2000 @04:03AM (#892795)
    Truth to tell no difference at all. Except, Debian always ships with much older and more stable versions of many packages. This way, it looks more stable as a whole.

    Either than this, they are all the same. They all package free (as in freedom) software developed by someone else.

    RedHat however has the best balance when it comes to ease-of-use/stability/quality/support....

    It has also built a good brandname, kindda like Sony for electronics. Sony stuff might not always be the best, but you know it's among the best.

    As for hardcore geeks prefering Debian. I think it's mostly the "I don't use what newbies use" attitude or maybe it's "I use something very few use"

    Anyway, conclusion: they are 90% same stuff with some version number difference.

  • We're normally in a 6 months release cycle - which I think is about right: Making even more releases would sometimes be nice for the technical side, but would definitely be scary for retailers.

    Making less releases would put us behind all the others (just imagine the slashdot announcement "SomeDistro 10.3 released, has Kernel 2.4.1 and KDE 2.0, while Red Hat is still at Kernel 2.0.38 and KDE 1.0" - nobody (except for some Red Hat haters, maybe) would like that!) - at the pace of development in Linux, 6 months can be a major change...

    We're not talking about 3-years-later-than-95-is-still-almost-the-same-OS. ..

    Changing that would be giving up some of the biggest advantages of Linux and (fast) open source development.
  • by bero-rh ( 98815 ) <bero@reCOMMAdhat.com minus punct> on Monday July 31, 2000 @04:04AM (#892804) Homepage
    s/needing/supporting/g

    For a normal install, you won't need the second CD. It's just there for some extra packages that most people probably won't need.
  • Interesting that they wouldn't include a beta of the kernel but of KDE

    We are actually including a 2.4 kernel package (I think it's on the 2nd CD), it's just not installed by default.

    The reasons are simple - you don't want a mission critical server to crash because of a broken kernel.
    While a UI segfaulting is not very nice, it's hardly as critical.
  • by troc ( 3606 ) <[troc] [at] [mac.com]> on Monday July 31, 2000 @04:50AM (#892809) Homepage Journal
    Wow, you are so intelligent, erudite and clever I'm amazed you lower yourself to our level. I find myself enhanced by the very presence of your posts here on Slashdot and am naturally swayed to believe everything you say purely due to you incredible qualifications, no doube gained at a particularly young age.

    I'm guessing from the quality of your post that you are also fantastically good looking, witty, urbane and generally perfect.

    Keep up the good work, we all know that there are very few highly educated Slashdot users around and we need reminding every now and then as to that which we should aspire to.

    troc ;)
  • Do any distros have palns to ship nVidia's official drivers with their distros?

    We'll start doing that as soon as they release the source. If anyone at nVidia is reading this, please cause the right consequences. ;)

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (1) Gee, I wish we hadn't backed down on 'noalias'.

Working...