Slashdot Mirror
Red Hat 7.2 Released
Spirit writes "Red Hat has anounced the release of Version 7.2 distribution with Gnome 1.4 and Nautilus, default ext3 fliesystem and according to ZDnet migration from LILO to GRUB"
Updated by HeUnique:There are some issues to note before upgrading: The kernel that comes with the RH 7.2 is heavily patched 2.4.7 and has been tested quite heavily on fully loaded Linux boxes - so the recommendation is to use it
If you're upgrading from the previous Red Hat 7.1 and you're using Ximian GNOME, then you might want to erase all Ximian GNOME RPMS (use the command: rpm -e `rpm -qa | grep -i ximian` --nodeps to erase the RPMS). Red Hat's GNOME RPMS has been more tested then Ximian's one and there is a conflict between them. You cannot use Red-Carpet on Redhat 7.2 as it will fail with the RPM libraries.
These are the most critical notes about Redhat 7.2. You might want to read the README & the Release-notes which appears on the 1st ISO image.
Oh, and if you already installed it - then have some fun with the new un-official RPMS from Enigma's section of FreshRPMS
To forestall the inevitable questions
-- why not reiserfs, xfs, jfs, etc.
First look at the total feature
list of ext3 and compare, in particular the
compatibility (forwards AND backwards) with ext2.
There may or may not be better candidates for
a fs, but there are certainly none better for
a default install.
Redhat has dropped support for Postfix (a sendmail replacement), which used to be on the Powertools CD. I really don't know why
.2 version, RedHat is going to support it for a looong time
;)
It's because Powertools was dropped, and everything on Powertools that conflicts with something on a main CD (e.g. you can't install postfix and sendmail on the same system) had to go because at this time, the installer doesn't handle conflicting packages (breaking the "Everything" install isn't nice).
This is likely to get fixed in a future release (no promises though, it's not my decision [I'm all for postfix]).
Those who prefer it can grab the current official postfix package from rhcontrib. I'll open up the 7.2 section there later today.
Since it is a
<obligatory "we don't preannounce releases" rant>
What makes you think the next release will be 8.0?
</rant>
This message is provided under the terms outlined at http://www.bero.org/terms.html
Not me - I did a bit of benchmarking but that is my sole contribution to nautilus. Lots of other folks both inside and outside of RH did all the work.
FAT? Hardly! ext3 uses is built on extension hooks designed into ext2, allowing you to mount ext3 partitions with an ext2-only kernel (of course no journalling in that case). Also, it takes a few seconds to "convert" ext2 to ext3, can't get easier than that! :-)
Personally I find it impressive that the foresight in the ext2 design allowed for ext3 to evolve the way it did with the backwords compatibility
And hey, it just works. Performance is like ext2, except you never have to fsck anymore when the machine doesn't shut down properly. And your ext2 bootfloppies still work, you don't have to reformat your partitions first, and did I mention it just works? :-)
So why not? ReiserFS would be more suited for news spool and squid cache partitions, but if you just want your same old system except for the fsck's, ext3 is the way to go.
gcc 2.96-RH is all open , always has been. Gcc 3 is not quite compatible so wouldnt be appropriate for the base tools for a new release. It is on the CD though if you want it
The only nonfree stuff on the RH distro should be netscape, and we recommend mozilla 8)
GNU GRUB != GRUB. I don't know which version this is, but RMS will be annoyed if they've left off a GNU... :D
/sbin/grub, it supports Logical Block Address (LBA) mode that solves the 1024 cylinders problem, and TAB completes a filename when it's unique. Of course, many bug fixes are done as well, so it is recommended to use GNU GRUB.
From the GNU GRUB Faq:
1. How does GNU GRUB differ from Erich's original GRUB?
GNU GRUB is the successor of Erich's great GRUB. He couldn't work on GRUB because of some other tasks, so the current maintainer Gordon Matzigkeit took over the maintainership, and opened the development in order for everybody to participate it.
Technically speaking, GNU GRUB has many features that are not seen in the original GRUB. For example, GNU GRUB can be installed on UNIX-like operating system (i.e. GNU/Linux) via the grub shell
http://freshrpms.net/misc/enigma.html
Also, don't forget to go get all the "missing" goodies (xine, lame, nessus...) from http://enigma.freshrpms.net/
Happy download! :-)
Matthias
UK folks should findu ti ons/redhat/7.2
ftp://zeniiib.linux.theplanet.co.uk/pub/distrib
nice and fast (its the new linux.org.uk test box)
Alan
I understand RedHat cannot integrate ipsec / FreeS/WAN into the Linux distribution because of US export restrictions.
I don't think the export restrictions you're referring to are still in place.
We're currently shipping cipe, which provides pretty much the same functionality.
There have been some reasons for choosing cipe over FreeS/WAN. I don't remember the details, but I think it was related to not supporting non-x86 arches.
This message is provided under the terms outlined at http://www.bero.org/terms.html
This message is provided under the terms outlined at http://www.bero.org/terms.html
We now have RedHat 7.2 up and running in the Compaq Test Drive Program, so you can try it on our systems before you put it on yours. It's running on a couple of dual-processor x86 systems, and using the ext3 file system. Sign up for a free account and give it a try.
kernel-headers-2.4.9-7.i386.rpm
kernel-2.4.9-7.i386.rpm
kernel-doc-2.4.9-7.i386.rpm
kernel-source-2.4.9-7.i386.rpm
kernel-BOOT-2.4.9-7.i386.rpm
nscd-2.2.4-19.i386.rpm
glibc-common-2.2.4-19.i386.rpm
glibc-devel-2.2.4-19.i386.rpm
glibc-profile-2.2.4-19.i386.rpm
glibc-2.2.4-19.i386.rpm
openssh-askpass-gnome-2.9p2-9.i386.rpm
openssh-2.9p2-9.i386.rpm
openssh-askpass-2.9p2-9.i386.rpm
openssh-clients-2.9p2-9.i386.rpm
openssh-server-2.9p2-9.i386.rpm
squid-2.4.STABLE1-6.i386.rpm
mew-1.94.2-12.i386.rpm
util-linux-2.11f-12.i386.rpm
-- You can be a geeklord too
Ximian GNOME for Red Hat Linux 7.2 has been released. Please don't follow the instructions in the article for removing Ximian GNOME, as that will break your rpm dependency tree pretty badly.
The recommended procedure for upgrading to Red Hat Linux 7.2 with Ximian GNOME is to perform the Red Hat upgrade, then immediately reinstall Ximian GNOME.
lynx -source http://go-gnome.com/ |sh
The mirrors will pick it up shortly.
Share and enjoy,
The Ximian release team
Just to re-emphasize, Hemos's instructions for 'cleaning' Ximian will seriously break your system- it'll remove glib (among other things) which will remove a large number of RH's system tools. So... don't.
Luis Villa [Ximian Bugmaster, who doesn't want to have to deal with 'Hemos broke my system' bugs all day]
IAAL,BIANLY
That's why I said "most" config tools.
/etc/sendmail.cf in key=value or xml, by the way?) - but it's almost certainly not going to happen, at least not anytime soon.
I know there are some exceptions (mostly due to schedules that had to be kept - we can't always get all wanted features into the first version...).
The non bandaid solution is to standardize on a particular format for config files
This is true - but I don't think you can get every project to follow the same standard.
We actually talked about something like this internally (basically, "provide one standard library for every config stuff, then fork every app to make use of it and ask maintainers to apply the patch"), but dismissed the idea quite quickly because that would definitely be a nonstandard thing giving people legitimate reasons to complain about ("Oh, you're using the Red Hat version of my application? Then I can't help you, I don't know anything about it, and I don't like their config layout"), and more "Red Hat is just like Microsoft, now they're forcing everyone to use their crap rather than compiling from source!" type FUD.
In an ideal world, we'd all be using the same format for config files (how do you represent
Even OSes that try to enforce one config scheme on everything (e.g. M$ registry) end up with applications that create their own config files using something totally different.
This message is provided under the terms outlined at http://www.bero.org/terms.html