Slashdot Mirror
Red Hat 6.2 Beta on FTP Servers
Bryan Mattern writes "I went to do an FTP install this morning and noticed RedHat 6.2beta on the FTP mirrors. There is no official word yet from Red Hat, but I'm downloading it right now. Might be nice to check out if you can grab it. " Update: 02/09 06:32 by H :You can also grab it from SourceForge's mirror.
Every day we get a new beta :)
(pity apt isnt installable atm, but thats what freezes are for, isnt it)
* Yarn pokes mirror.ac.uk and decides to check if it has the required packages now
-Yarn - Rio Karma: Excellent
You might call Piglet a snapshot of Rawhide. Or not.
-E
Send mail here if you want to reach me.
I was unimpressed by Mandrake 7.0. It did not properly detect my sound card (Red Hat 6.1 did), and while the enhancements to KDE were appreciated, Red Hat's unenhanced KDE wasn't any harder to use once you dragged a few icons a'la Mandrake out onto the desktop. And Red Hat 6.1 comes with PostGreSQL support already pre-compiled into all the web languages (Python, Perl, PHP3), so that you can sit down and write database-enabled web applications without ever installing a single software package. (Hopefully Caldera 2.4 will do this with MySQL too). Mandrake 7.0 also doesn't come with OpenLDAP or pam_ldap.
In short, Mandrake 7.0 wasn't much better than Red Hat as a workstation, was worse than Red Hat as a server (the most common use for Linux, after all), and I just didn't have much use for it.
-E
Send mail here if you want to reach me.
IMHO, whenever the errata exceeds 50MB, an automatic version increment should occur.
Let's face it: not everybody is on a T1. This will also encourage Red Hat to do it right the first time (witness the Apache upgrades for 6.1).
I don't know what the Slashdot policy on this is - it would probably be good to delete the user.
Please don't moderate this up.
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
If you don't have a testbed server to play with 6.2, I suggest waiting a month until the product is officially released, then grab and install this; by this time, the major security bugs will have been found and errata'ed, and you'll know of any possible quirks in the install if you follow the right discussion boards.
"Pinky, you've left the lens cap of your mind on again." - P&TB
"I can see my house from here!" - ST:
Whasn't the beta releases named rawhide?
What ever happened to the rawhide distrobution? Did they simply give up on the idea on rawhide, and now just name things beta?
-- I'm the root of all that's evil, but you can call me cookie..
Bruce
Bruce Perens.
True most of the time, perhaps. Every once in a great while you have to upgrade because of software, too.
Case in point: I have been running RH5.2 happily for about a year, but I really really wanted to try out Mozilla. Of course, none of the recent builds are recommended for glibc2.0 (RH5.x), because of bugs that get fixed in 2.1. And nobody would build binaries for us little glibc2.0'ers, because what was the point? It wasn't stable anyway. I tried, but somewhere in the middle of the build I realized that clearing out over 600MB of space wasn't going to be enough, and dumped it. *sighs*
So, I tried the upgrade to 6.1 yesterday. And somehow the FAT table on my poor DOS partition was destroyed. I swear, all I did was choose "upgrade." This being a work computer, it's important that I have a partition for Windows (even though I was able to run most of the apps via WINE).
Anyway, now I'm flailing around, trying to get work done without anyone knowing that I've lost every ounce of my Windows stuff. Point is, sometimes you get lost in the cracks (like I did), and have to deal with either upgrading or actually falling behind. (But I learned my lesson: next time, I'm either going to do the install completely manually, or dump the whole thing and try Debian.) *smiles*
What are they doing at RH? With all the fiscal support they've been getting, I'd expect some pretty amazing advances in terms of installs and upgrades. Oh well. It's not my problem and I have nothing to contribute, so I'll just shut me gob!
**>>BELCH
Oh come on - it's not like this is a major ethical transgression on slashdot's part to announce that a new unannounced beta has been released.
In fact, it's their bloody job. This is news on the internet, which means that time on the scale of hours is critical. Sure, it would be "nice" of slashdot to coordinate everything with Redhat, but they can't do that.
I for one want to hear about these things as quickly as possible, because that's what slashdot is good at for me - speed. If I want to hear it after it's official and all the mirror sites have a copy, then I'll bloody well read a press release off of RedHat's site when they announce it.
-- Truth goes out the door when rumor comes innuendo. -- Groucho Marx
The mirrors started syncing it since noon Central time yesterday, i snagged me a copy of the iso by 4pm, and the installer is much better than in 6.1
This is what 6.1 installer should have been like. They finaly made an option for you to use fdisk instead of stinky diskdruid during the gui installation.
Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
Check out the period "." at the end of the name. Slasdot guys, shouldn't this be grounds for cancellation of an account..?
----
Before we begin with all the posts about how Red Hat is simply inflating their version numbers, etc, etc, let's take a moment to look at the past Red Hat release schedule...
Oh yeah, comes out about every 6 months, like clockwork. That's a good thing, IMHO - if you want to stay on the cutting^H^H^H^ fairly sharp edge (and of course you don't HAVE to....) there it is, all wrapped up with a bow on it.
----
ALthough I use mandrake 7 and enjoy it greatly (as a client machine -- not so much as a server, as I prefer FreeBSD) -- you might want to get the supermount patch from freshmeat.net, and patch it into a vanilla 2.2.14 kernel. It should compile cleanly from that point on.
Three Step Plan:
1. Take over the world.
2. Get a lot of cookies.
3. Eat the cookies.
perhaps an account name should not be exactly the same as another with only punctuation or spacing as difference? a little intelligence in the name checking would go a long way.
I've finally had it: until slashdot gets article moderation, I am not coming back.
Bah. This method truly SUCKS on remote hosts, because you must manually REVOKE the cookie afterward on the remote host. If several people can su root on that host, they can steal that cookie and keep it even if you revoke it. Whereas with xhost, at least I can remove the xhost access.
... which is why it's made impossible.
I want to be able to xhost +COOKIE:LARGE-HEX-NUMBER, which I could just generate on the fly, then transfer to the remote end. When finished, I could just drop it from xhost, neatly revoking authorization. Steal the cookie all you want, it's useless now.
At the very least, I'd at least like to just create new xauthority entries. try it yourself sometime with xauth generate. works exactly once, defeating the purpose.
That would just all make sense
I've finally had it: until slashdot gets article moderation, I am not coming back.
It also has done something to X windows now. I usually am able to su - to root in an xterm and then export DISPLAY=:0.0. and run certain programs as root in X. Now I get xlib connection refused. I'M ROOT!!! How the hell can you refuse me a connection??????
You shouldn't need to export your display. As a user, enter "xhost +localhost" into your xterm. Be sure to then shut off access via "xhost -localhost" when you're done doing whatever it is you have to do.
--Cycon
Your Brain + EEG + LEGO Robots = Brainstorms
Well, Everyone's said this already, but since you asked. Mandrake isn't RedHat with KDE anymore. It is their own distribution, which just happens to use RPM as the package manager. Just like Corel isn't Debian "with fixes".
Okay, this is really what I wanted to respond to.
Whats to stop Microsoft from creating their OWN Linux distribution?Nothing, and who cares. I mean, if they do, and people use it, I won't need to. Sure maybe I'll lose out the ability to run some applications that are written for MS Linux, but I can't run MS Apps now anyways.
I doubt Microsoft will ever release a Linux distribution. It just wouldn't be profitable for them. It goes strongly against their belief that people don't want "free software". However, I do think that they will make something to "compete" with Wine, so that their apps will run under Linux. But that'll only happen when they *know* that they've lost the market to Linux. At that time though, I forsee a "Windows for Linux" product on shelves. Just wait and see...
-BrentWhen I installed Mandrake 6.0 I noticed the same thing, but I made a small hack to Xsession to check for the existence of a file in $HOME and invoke the appropriate desktop. It seemed neither nontrivial nor nonobvious, but I suppose I can put up the details later (when I'm at home on my Mandrake box). :)
This is my opinion and my opinion only. Incidentally, IANAL.
MOO;IANAL.
There used to be a picture linked here.
send flames > /dev/null
Only 'flamers' flame!
It also has done something to X windows now. I usually am able to su - to root in an xterm and then export DISPLAY=:0.0. and run certain programs as root in X. Now I get xlib connection refused. I'M ROOT!!! How the hell can you refuse me a connection??????
My next letter of complaint is going straight to them to let them know that I extremely disappointed in this release. They are becomming just like so many of the other crap companies that are selling Linux distros. They care less and less about the seasoned user and more and more about the newbie. While it is great that they care about the newbie, but they need to realize that when they hoze up someones system that they can really piss people off. Like ME!
signed one dissatisfied Redhat 6.1 customer.
send flames > /dev/null
Only 'flamers' flame!
I do have backups and I have been using Linux for many years myself. The fact that there installation did not ask me if I wanted to install lilo really pissed me off. If I did not know what I was doing I would not have just booted my system and done lilo -U to restore my nt boot and then reconfigure my system. My system is firewalled so I do not care about xhost+ enableing access to my system, becuase the port is closed to ALL except :0.0
The issue is that Redhat's distro assumed that I wanted things there way, and did not let me do it my way, and thus I have to reconfigure a server now that causes downtime which if I were a buisiness it can cost money!!!!!!!!!!!!!!!!
send flames > /dev/null
Only 'flamers' flame!
send flames > /dev/null
Only 'flamers' flame!
with a last updated stamp of 01/01/97.
In light of the recent DoS stories I thought this might be interesting to some people.
Imagine someone sent this into slashdot:
"I went to do an FTP install this morning and noticed a hidden folder under ftp://ftp.microsoft.com/bussys/sql containing tons of pre sp2 hotfixes for sql7.0. There is no official word yet from microsoft, but I'm downloading it right now. Might be nice to check out if you can grab it. "
Would anyone care? Of course not. Cause it's not news.
If you found a tcpdump log on the ftp server showing that bob young was the grits guy, that would be news. Finding a beta release 12 hours before a press release is issued isn't news.
--Shoeboy
I think theres a reason they don't announce the beta right off the bat and it's probably (just maybe) so they can get the distribution out to mirrors so their core site doesnt get slammed.
Jeezus, do you think we could be just a tad more responsible when making these kind of announcements?
~dlb
Don't use xhost +. That leaves your system open to anyone. Someone could start a hidden X program that looked at the keystrokes you were entering and snag your passwords. That's one of the reasons xterm has a secure keyboard mode.
"When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
1) Nothing prevents microsft from doing this.. and though it seems wierd, they are welcome to do it.
2) Adherence to open standards will still save us.
Microsoft banks on all their proprietary software to keep people buying nothing but MS.
If they were to bring out a linux platform, they would lose that edge. Anyone could develop apps...
But what.. you say.. if MS uses the linux kernel, a full complement of linux apps, and then puts their own proprietary UI on it? Well... good for them. Is it X compatable? If not, it might not fly. If it is... that's just fine with me. What if they develop all their apps to require their proprietary GUI, and others do as well? Hmm... this is a bit outside of the OSS stuff we are use dto.. but they still don't control the back end. The choice of the MS GUI over others *would* be based on performance. If make a package that lets the windows destop work with linux behind the scenes... all the better for me. Developers would be *very* quick to use the image of a 'windows' platform with the ease of development of a unix backend to create some cool apps.
#1 wish of server operators: better administration tools. LinuxConf's GTK+ frontend is buggy and poorly designed from a user interface point of view. Occasionally the program exhibits other weird behaviors too (not changing things it said it would change, etc). And it's still not that comprehensive.
Check out Corel's video settings tool in the KDE control center. THAT is something I've wanted for YEARS. Webmin, by the way, is much nicer to use than any form of LinuxConf right now. Really, though, I don't need for one tool to be comprehensive, but I DEFINITELY want a central location from which to configure things, even if some of those config utilities are command line. This is an area in which many commercial OSes surpass Red Hat, but it should also be a relatively easy part to fix (which is tougher, writing a nice config interface, or scaling to 32+ processors?). Please, please work on this.
--JRZ
Ahmen to that my brother. I watch the redhat-install mailing list and there were many problems with 6.1 when it hit the streets. I have stuck with 6.0... I might go with 6.2 ...I dunno. They have hopefully fixed all of the 6.1 bugs by now.
Then again, my system is a running like a friggin tank on steroids, maybe I should just stick with 6.0 until I *need* to change. It's fun to try the new stuff, but I'm actually pretty happy that I'm not on that "forced* upgrade cycle anymore.
That's the great thing about Linux, if it's not broke, or you don't need the latest hardware support, you can keep running what you have.
The kernel in 6.2 as per the mirrors is 2.2.15 .
If Microsoft was never created, who would we have to hate?
[nonroot@mymachine homedir]$ xauth list
mymachine:0 MIT-MAGIC-COOKIE-1 LARGE-HEX-NUMBER-WHICH-IS-THE-COOKIE
mymachine/unix:0 MIT-MAGIC-COOKIE-1 PROBABLY-THE-SAME-LARGE-HEX-NUMBER
Go root and add the authorization cookie to root's xauth file. Since you are on the same machine, and on the console, you want to copy the line that says mymachine/unix:0:
[nonroot@mymachine homedir]$ su - root /root]# xauth add mymachine/unix:0 MIT-MAGIC-COOKIE-1 LARGE-HEX-NUMBER
Password:
[root@mymachine
Now, export display to the console:
[root@mymachine /root]# export DISPLAY=:0
Now everything should work.
Although typing: xhost +localhost seems more economical, it opens you to "X attacks" by any one with login access to your machine (attacks such as popping whatever X programs on your screens or being able to know whatever programs are running on your X and killing them or sending any X events to them). Besides, some sensitive X programs (particularly those that are supposed to be run by root) simply refuse to run on displays with xhost +whatever-machine because of the unsafety descibed above.
-----------
"You can't shake the Devil's hand and say you're only kidding."
I believe you 8^)
I checked install everything on Mandake, and it left me happy - sorry you didn't have the same experience.
In terms of major distros:
I can't remember what I used around kernel 1.0.x
I used slackware starting in the early 1.2.13 days (pretty nice, especially for the time)
Redhat led me into the 2.0.x days, after I had compared Slack and Redhat... then I started using Mandrake this past summer, and I was really impressed by some of the ups (and dissapointed by the downs of course). Haven't tried suse yet, though I've got the CD right here. Helped a couple people with Debian... but not a whole lot of personal use.
Mandrake kept me happy, and I was able to do all the devel work that I needed to do w/o any extra effort. I tend to remove most default rpms after I start using them to roll my own for the newer releases (apache, anything that uses CVS). RedHat and Mandrake both contributed to my dislike of rpms, and life goes on.
I wasn't trying to criticize you, or RedHat - again, just relating my experiences.
(BTW - no distro has a good *default* install yet. Even with the 'workstation' and 'server' presets that some offer. This includes any version of windows, too 8^)
"It's tough to be bilingual when you get hit in the head."
If Redhat's marketing make a thing about their installer being easy to use, and it blatantly isn't, then the poster might have a case. I don't think MS claim their *installer* is easy to use, so you probably can't get them on that.
perl -e 'fork||print for split//,"hahahaha"'
Also, does Red Hat support the Highpoint HPT366 ATA/66 chip?
--------
Oscarfish.com: tropical fish with attitude. Way t
It also installed lilo which is something I did not want to do since I use the NT bootloader on my dual boot machine. If it had recognized or warned me about the installation of lilo it would have been one thing, but it assumed I was a "know nothing about linux person" (newbie) and I am NOT
I must say that is very stange. I have installed 6.1 on numerous machines (5 at least, including one this afternoon), and I always got a screen asking if I wanted to install LILO or not... it was at the same place it asked if you wanted to make a boot disk before it starts installing. All this was in the normal non-expert mode. However, I must note I've never upgraded from 6.0 to 6.1.
I must note that on X-Windows, I've never had any problem su-ing and running programs (such as rp3-config) as root.
If you're really unhappy, try FreeBSD or OpenBSD. BTW, don't let the rumors about OpenBSD being hard to install fool you. I did it this afternoon (OpenBSD 2.6) with very little trouble (the disk configuration program is confusing at first but it's not that hard). However, it didn't like the PCMCIA Ethernet card and the drive was promptly nuked for RH 6.1.
And the stable kernel is only 2.2.14! Better get Windows 95!
I can see the headlines : Another popular site victim of a DoS attack...
-----
cheers
I had replaced sendmail with postfix, and the upgrade stomped on it, reinstalling sendmail.
Then you did something wrong.
You probably didn't rpm -e sendmail, so the installer saw sendmail was installed and needed to be updated.
Or, you installed a broken postfix RPM that doesn't provide smtpdaemon, so the installer saw there's no smtpdaemon and resolved that dependency by installing sendmail.
This message is provided under the terms outlined at http://www.bero.org/terms.html
We're currently working on it.
If you've checked the beta, you've probably noticed the
wuftpd-config
printer-config
apache-config
squid-config
firewall-config
packages.
They're a start. There will be a central tool for them all, but we probably won't finish it in time for 6.2.
This message is provided under the terms outlined at http://www.bero.org/terms.html
We'd like to include OpenSSH - but the stupid RSA patent doesn't allow it.
This message is provided under the terms outlined at http://www.bero.org/terms.html
In the mean time, you can download official Red Hat packages for both ssh and openssh from our German servers. ftp://ftp.redhat.de/pub/rh-addons/securi ty.
This message is provided under the terms outlined at http://www.bero.org/terms.html
The 6.1 installer was indeed a bit rushed - little more than expectable, considering it was completely rewritten.
6.2 fixes most known bugs.
This message is provided under the terms outlined at http://www.bero.org/terms.html
why does redhat insist on upgrading the sendmail even if this package was uninstalled
<br>
Because you installed a broken qmail package.
You need a package that Provides: smtpdaemon, or the installer will resolve that dependency by installing sendmail.
This message is provided under the terms outlined at http://www.bero.org/terms.html
No, 6.2 is still with egcs for compatibility reasons.
7.0 will have a current gcc (whatever is current by then - probably either 2.95.4, 2.96 or 3.0).
This message is provided under the terms outlined at http://www.bero.org/terms.html
Well, I haven't tried this 6.2 beta yet, but after 6.1 I am starting to get more and more of the impression that it's going way too much Windows direction. It's no longer about understanding things and how they work, but rather about knowing "when it says this it in fact means this-and-that" and "if you want to do this (e.g. fdisk) you must pretend to do something else to get the first thing done". See also "Insert Driver disk", missing descriptions of packages in 6.1 text install, overall feeling of losing control over the installation of the system, unhelpful help (or none at all) etc..
So in this light it's a piece of good news that the installer got better.
To your "root in xterm" problem - just do xhost +root@localhost or something to that effect before you do your su, DON'T do xhost + as it could be pretty dangerous (anybody could send you an X client which would grab your keyboard, snoop your keys and whatnot)..
Try this:
# export XAUTHORITY=/home/user/.Xauthority
(where user is the owner of the display you want to use - it's safer than xhost)
Slashdot? Oh, I just read it for the articles.
and building with -g on glibc and linking with it (putting it in /etc/ld.so.conf) did provide the line #'s (and other symbols I needed - FROM MY APP).
and repeating the same experiment on a redhat system I had at work also gave me line #'s in my gdb session. so go figure - but the truth remains; even when I specified 'install all' on both distros, redhat let me develop and DEBUG software whereas mandrake was too concerned with keeping the lib as fast and small as possible.
--
--
"It is now safe to switch off your computer."
on redhat, the default install is "install all". ie, everything that has an rpm. so whenever I have enough disk space (almost always) I check "install everything".
so THAT wasn't the problem. again, it REALLY was mandrake - not me that was at fault.
--
--
"It is now safe to switch off your computer."
what do I mean by this? when debugging even an ultra simple prog, there were no symbols in libc so my gdb session was essentially worthless. to prove it, I downloaded all of glibc (whew!) and built it (took hours on my dual celeron 466) - then linked my prog against that lib. voila! got my debugging symbols.
emailed the mandrake team and they had little to say. so I jumped ship and went back to redhat.
--
--
"It is now safe to switch off your computer."
From an Anonymous Coward, "DES sucks. Let's see Blowfish, RC4, RC2, Twofish, IDEA, RSA, 3DES, Safer, etc. on the standard, precompiled, linux distros (with the crypto source already in there too).
I want to be able to create encrypted file systems right out of the box. It should even be an option in the setup program. That way, when the MPAA/RIAA kick down the door searching for copies of DeCSS or MP3s, you can just hit the power switch and be safe."
What I wouldn't do for the ability to create an encrypted file system right out of the box. I'm so sick of hearing stories about Government granting searches of home computers.
Joseph Elwell.
Since nobody else seems to have the full thing posted yet, and it's funny:
/etc/fstab
Tired of collecting Beanie Babies and Pokemon cards?
Christopher Robin called last night complaining about the lack of collectibles pertaining to the famous "Pooh" show. Eeyore, of course, said,
"I dooon't knooow aboouuut this".... But what does Eeyore know anyway?
The result:
PIGLET
This is no ordinary pig! Stand back folks, he's large and live and ready to rumble. This pig is knocking back CPU loads of 99 whilst having tea and crumpets with Pooh Bear. This bad boy eats Lizards for breakfast and spits out kernel patches. Approach with caution, he could be dangerous!
PIGLET: Your once in a lifetime chance to have this rare collection!
This is a limited time offer, when we run out of bits, they'll be gone forever. Don't miss out folks, the Internet lines are lighting up, they're going like hotcakes, and we can't guarantee availability on this item for very long! Similar items we have provided in the past are now going for over a ONE MILLION percent gain on the original price tag of $0.
PIGLET includes the following new features:
- A new and improved Anaconda [tm] installer
- Partitionless installs
- Improved X Configuration
- Additional GUI Partitioning tool
- Software RAID Configuration in Kickstart Installations
- RAID upgrades
- ATAPI Zip and Jaz Drive Recognition
- Rescue Disk Improvements
- It works!
- Rescue via the installation CD
- Pico on rescue disk
- mtools on rescue disk
- Kernel 2.2.15
- Enhanced Software RAID
- P III Enhancements
- New web based High Availability Configuration Utility
- Kerberos Integration
- New Window Managers
- New desktop backgrounds and themes
- Docbook tools
- Standard Samba mounts in
- Smaller minimal install
- Separate client/server packages for servers:
PIGLET, pick up this rare find at:
ftp://ftp.redhat.com/pub/redhat-6.2beta/
Or at a mirror near you! A list of Red Hat ftp mirrors can be had via your web browser of choice at:
http://www.redhat.com/download/mirror.ht ml
PIGLET is available now for Intel, Sparc and Alpha architectures. PIGLET is ONLY available through the Internet, and ONLY for a limited time!. This is a beta release of Red Hat Linux, and we don't encourage using this for mission critical applications. However, like most Red Hat beta collectibles, it is very usable for:
1) Testing those new holographic storage devices
2) Installing on all of the machines in your favorite lab
3) Seeing what that "Linux thing" is really all about
4) Preparing your thesis on "Works in progress"
We have created piglet-list for discussion of this beta release. To subscribe, merely send a message to piglet-list-request@redhat.com with the code word "subscribe" in the subject line, respond to the confirmation message request, and enjoy hours upon hours of entertaining and useful messages from hackers trying to make this thing fall down go *BOOM*...
(With a special thanks to home shopping channels everywhere!)
If Rob deletes the "Bruce Perens." account, then the imposter will simply create a new account. Deleting the account doesn't quiet him; it just gives him extra attention. At least we know the "Bruce Perens." account is fake and can warn other people.
cpeterso
Just got the email from RedHat. Here's some features of what's new. /etc/fstab
PIGLET includes the following new features:
- A new and improved Anaconda [tm] installer
- Partitionless installs
- Improved X Configuration
- Additional GUI Partitioning tool
- Software RAID Configuration in Kickstart Installations
- RAID upgrades
- ATAPI Zip and Jaz Drive Recognition
- Rescue Disk Improvements
- It works!
- Rescue via the installation CD
- Pico on rescue disk
- mtools on rescue disk
- Kernel 2.2.15
- Enhanced Software RAID
- P III Enhancements
- New web based High Availability Configuration Utility
- Kerberos Integration
- New Window Managers
- New desktop backgrounds and themes
- Docbook tools
- Standard Samba mounts in
- Smaller minimal install
- Separate client/server packages for servers: