Posted by
justin++
on from the that-was-fast dept.
adraken writes "It just seems like minutes ago that 2.3.1 was out, but 2.3.2 is out... " Remember folks: use a mirror. Standard "don't use unless you know what you're doing" disclaimer applies.Update: 05/15 02:43 by J: There seems to be a ChangeLog available.
84 comments
Re:problem?
by
Anonymous Coward
·
· Score: 0
They are work in progress and thinks might be buggy or broken in that process.
Re:Please stop posting devel kernel releases.I tot
by
Anonymous Coward
·
· Score: 0
I totally agree with you. Please, Rob, don't post each and every update to 2.3.2... 2.1.x went up to over 130 before we hit 2.2, and considering there are only maybe 10 stories posted per day, let's not waste one or two of them on kernel updates that we can find out about many other places if we want to know.
Thanks for the kernel releases!
by
Anonymous Coward
·
· Score: 0
I like them. Please keep them around.
I understand that people will want to filter them; maybe you can make a special type of story that is easily filterable.
Re:question about framebuffer
by
Anonymous Coward
·
· Score: 0
That's exactly what it's good for. Have you seen a fully graphical, one-floppy linux install? You will.
(and no, I'm not counting Caldera 2.2 since it doesn't work in 99% of real-world installs)
Re:Your perl scripts are buggy Rob!
by
Anonymous Coward
·
· Score: 0
I'm sure, anybody who's interested in this have subscribed a linux-mailinglist or something like this or can read it on freshmeat.
Solution: How about a Slashdot Bar?!?!
by
Anonymous Coward
·
· Score: 0
I think that will work a lot better, keep the latest release announcements up there, and you can add/remove it if you desire.
A new kernel every day...
by
Anonymous Coward
·
· Score: 0
...this is exactly what *BSD does, it's called *BSD-current. You can sup&install a new kernel every day if you want. You can even sup&make a new world every day if you want...
Like Linux devel kernels, *BSD-current ist not for the "average" and not guaranteed to be stable or working well (but in most cases it is!).
The only difference to linux is that *BSD doesn't change the kernel version every day.:-)
I really like the idea of "current" and I think "bleeding edge" linux users would love this too.
Does kernel.org offer sup? I've browsed the website and only saw ftp and http. Why don't they support sup? It makes life much easier if you always want to have the latest sources.
Re:question about framebuffer
by
Anonymous Coward
·
· Score: 0
Not just Debian. RH and SuSE are working on them as well.
Re:question about framebuffer
by
Anonymous Coward
·
· Score: 0
The VGA 16 framebuffer is useful for anyone who doesn't have a VESA compliant video card. VGA16 is likely to work on any VGA card.
Re:question about framebuffer
by
Anonymous Coward
·
· Score: 0
Alan Cox was involved. He works for RH.
Already available! (Don't use 2.3)
by
Anonymous Coward
·
· Score: 0
Hey all! Yeah, I noticed that, and I think it's GREAT! BUT! I do *NOT* think this is a reason to use 2.3. After all.. v2.0 and 2.2 already _*HAVE*_ a rw driver! I have been wondering for QUITE a while why it wasn't included in 2.2, and I found out when I went to go d/l a newer version of the driver. It was rewritten at 2.1.13x, the very end of 2.1.x, so there was little (if any) chance for a major thing (ro-rw? Big!) to be included in 2.2. However, I d/l'd it, and installed it on 2.2. (2.2.0pre(Something) iirc.;) And I'm still using it. (2.2.9) Works fine/great! So yeah, this is NOT a reason to use 2.3, however, since 2.3 recently branched, it MIGHT be okay to grab stuff out of 2.3 and replace the 2.2 stuff with it yourself, but I think the better idea is grabbing each individual driver, seeing what the author has to say about using it with 2.2, and replacing the current with it. The page for the hpfs (rw) driver is Read-Write HPFS Driver for Linux, http://artax.karlin.mff.cuni.cz/~mikulas/vyplody/h pfs/index-e.cgi
So, go check it out! There's a chance that 2.3's is newer, but I REALLY doubt it! Hope I could've been of help!
(Actually, I posted a similar question on the 2.2.7 (or 6?) article, asking about the hpfs modifications in that 2.2.x)
To see how the (at least some) development community feels about SlashDots' posting stories about Devel kernels, do a search on Deja.com for "slashdot" in recent days.
Sorry about the AC post, at least the initials march.
Thats part of being a linux newbie. Sometimes you to live and learn. I'm not suggesting newbies download devel kernels, I'm just saying that learning the hard way is not always bad.
Re:Why not just announce new kernel features?
by
Anonymous Coward
·
· Score: 0
You can really only speak for yourself.. I personally enjoy reading about updates. I still think it's a very good idea to make a different "topic" so that those who are not interested may filter away. Instead of using "Linux" and the penguin, how about "Linux Kernel Updates" -- any ideas for the picture? Maybe instead of constant bickering (not just on this topic, but on all topics by all people) maybe you can look at it from a different angle? Is there any good reason NOT to post something? No, just make it a new section and filter it. That way you only have to worry about it the first time it's posted - although if it's posted in the wrong topic, then... OH WELL that's another story;) nuff rambing from me.
Posted Anonymously to avoid moderation from being undone.
Re:question about framebuffer
by
Anonymous Coward
·
· Score: 0
Ahead of everyone else? Caldera's already gone to market with it.
Whatever.
Please help me!
by
Anonymous Coward
·
· Score: 0
Anyone experienced problems booting with a new kernel? I compiled 2.2.9 friday and when i boot i just see Uncompressing xxx....... and i'm returned to the lilo prompt. 2.2.0-2.2.4 compiled and booted fine but 2.2.9 was compiled with a new egcs (1.1.2) and a new binutils (2.9.1.0.23). I really don't know what can be wrong? Maybe a problem with my egcs/binutils? But i compiled a lot of stuff with this like fileutils, sh-utils, textutils, util-linux, procps etc and all is working fine. There are 2 entries at my lilo.conf. linux for 2.2.9 and linux1 for 2.2.4. TIA
I may be behind the times but I thought you had to use gcc for kernels for some reason. I'm running 2.2.8 with no probs.
Re:Bitkeeper? (or similar Source Management System
by
Anonymous Coward
·
· Score: 0
Yes, Linus said basically that he's going to switch to Bitkeeper in the future. It just wasn't ready enough for the launch of the 2.3 series. I'm sure Larry McVoy and company are workind hard on it as we speak.
Re:Just Wondering...
by
Anonymous Coward
·
· Score: 0
Well, that's just fine with me, this way bugs and 'features' are fixed quickly. If M$ did release bugfixes that fast most of us would be using NT.
Re:A new kernel poem
by
Anonymous Coward
·
· Score: 0
There once was a lamer named Nermal Who wanted a shiny new kernel He did not use patch So he clogged up the hatch and caused many a ranting infernal
If you think they are a waste of space (and time) Then: Don't click on articles pertaining to them Don't post messages about them Just ignore dev kernel release articles Are the people who run slashdot under your pay? I don't think so...
Slashbox proposal...
by
Anonymous Coward
·
· Score: 1
I know that there is a slashbox available for kernel releases already, the LinuxHQ box. How about expanding this box slightly, so like the poll slashbox, there is a link for people to post comments. The comments could be cleared after every new release.
In this way those that are interested in reading kernel anouncements have a handy single source of announcements and furthermore a forum to discuss them (yeah, I know the right place to discuss problems etc is on the kernel ml, but for other issues that aren't appropriate there).
I think most people will agree that they are a waste of space in the main news section, but there is definitely enough people to warrant there inclusion somewhere.
Opinions??
question about framebuffer
by
Anonymous Coward
·
· Score: 3
I noticed on the changelog for 2.3.2 that it has
16 color VGA framebuffer console driver added.
So what exactly is this? Is this along the lines of a stripped down GUI for the console? (obviously not something to the extent of an X server.) I'm guessing a use for it would be akin to Win95's install, where it dumps to a low color GUI for the entire thing. Anyone care to shed some light on this?
(sorry for the AC post, as moderating the thread from evildoers and for insightful users prevented me from posting )
Re:question about framebuffer
by
jcurbo
·
· Score: 1
Oh and if you are interested, you can find the archives for the debian-boot list at the Debian mailing list archive page. They had an example boot disk made (it would show you the copyright screen but had no hard disk support or such so that it wouldn't actually do anything) but I can't remember the address for that.
Re:question about framebuffer
by
jcurbo
·
· Score: 1
Ah. As I don't keep up with RH and SuSE I didn't know this. I believe the person who wrote the vgafb driver is a Debian developer though...
Re:question about framebuffer
by
jcurbo
·
· Score: 2
> That's exactly what it's good for. Have you seen a fully graphical, > one-floppy linux install? You will.
Yes you certainly will, if you use Debian in the future. As we speak the Debian boot-floppies team is working on a graphical installation disk set for a future release of Debian. It won't exactly be one-floppy (it's hard to fit the 2.2 kernel and the root.bin ramdisk on one floppy) but it will certainly be much nicer than the old newt-based install.
Re:question about framebuffer
by
John+Campbell
·
· Score: 1
Near as I can tell, Alan's involved in everything.
Re:question about framebuffer
by
scrytch
·
· Score: 1
Will you still have to page through each and every possible dselect package to install it? vi, vim, vi-swahili, vi-lower-slobivian, vi-ad-nauseum...
-- I've finally had it: until slashdot gets article moderation, I am not coming back.
Re:question about framebuffer
by
ioctl
·
· Score: 1
Well, it really doesn't matter who wrote the vgafb, it just matters who uses it better. IMHO, Debian is ahead of everyone else in this respect, so I think they will have the better one. Of course, I'm sure RH and SuSE will do an excellent job with theirs. =)
Always posting new kernel releases.
by
Jonathan+Hamilton
·
· Score: 1
Those people who don't like to have to look at the small title and articles for new realease of kernels don't have too. I might be the only one, but if you sign in and goto prefrences you can select what articles see or don't see. I use this so I don't have to read all the damn star wars articles.
I'm expecting to see the development kernel numbers climb pretty rapidly.. Probably a new one every day, with the occasional twice-a-day ones and the occasional skipped day.
Perhaps Rob/Hemos/someone can make a special 'Kernel' or 'Kernel-Development' news type that people can filter out. I'd actually recommend both types. That way, normal people can hear about the fixes to the stable end of things, and the people that love the bleeding edge can go out and grab the devel kernel..
Of course, I'm sure someone could just write a nifty script that fingers linux.kernel.org to update that stuff automatically (or maybe a slashbox.. hmm..)
A slashbox sounds like a great idea. Saves work for Rob and crew and lets us filter or not. Motion seconded.
Skippy
-- "False modesty is the refuge of the incompetent." - The Stainless Steel Rat
Announce ALL stable kernels, only important devels
by
Micah
·
· Score: 1
On one hand, I enjoy reading Slashdot discussions of the new Linux kernels. Success/failure reports are good, as are discussions of new features of kernels. A Slashbox, while good for announcing them and keeping up with the latest, wouldn't allow that discussion.
But please only announce development kernels when there is some REAL news. Like when USB is mostly working, or when the journaling FS is added.
I was informed of this a couple days ago. The "edge.linuxhq.com" (I think?) slashbox will show you what kernels are current (both devel and stable). Pretty useful, and it would be moreso if kernel updates weren't already announced on slashdot all the time...
- A.P. --
"One World, One Web, One Program" - Microsoft Promotional Ad
-- "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
Re:Stop posting 'Stop posting linux kernel updates
by
John+Campbell
·
· Score: 1
The latter is obviously a greater waste of bandwidth. It contains zero useful information, whereas the former contains the information that there is, in fact, a new kernel out. The signal-to-noise ratio of the news about the kernel updates, however low, is therefore infinitely higher than that of the whiners, which is zero.
Can we all stop whining? There are only a small number of types of whines, and if you see it once, please don't post the same stuff again. If you want to add more, post to the original whine. I'm sick of shorting through all this shit. I miss the days when people would put up their questions and stories about their experiences with a new version.
Re:Why not just announce new kernel features?
by
C.Lee
·
· Score: 1
>Looking at the Changelog, it seems that the real news here is: Centaur C6 MCRs now supported. Does that deserve a Slashdot article? I think not.
Of course you Mircosoft flacks would think this because posting a "bunch of kernel updates" as you losers express it on Slashdot exposes the lies (See the Mircosoft "Linux Challenge" WWW page for an example of this) that the Mircosoft PR department and it's allies try to spread about Linux for all the world to see.
How? Filter out everything relating to Linux? A "Linux Kernel" category would be nice. I can't imagine what the icon for it would be. But really, unless there's something significant about a new kernel, I don't see why it needs to be posted. Especially since the hackers are in the development tree now, and kernels are going to be popping up once every few days.
If you ever want to see the data on that HPFS partition again, don't. Using a development kernel, you're assuming that you will lose all your data. Be careful.
Some of them (2.1.44 comes to mind) can even trash your file systems.
Mind you, it sounds as though 2.2.8 could do that for you, too. That said, the `stable' branch does get a lot more attention paid to stability before each release, so you should at least bear that in mind before grabbing whatever the latest 2.3.x is now.
With a new slashdot forum automatically created for new kernel releases, in case people want to discuss them. Obviously only important new releases should get a mention in the `main' slashdot. Perhaps only post if a new release is seen as a major milestone, or if it contains fixes for a major data loss/security problem (e.g. 2.2.0 would have been announced. 2.2.9 would probably get a mention because of the filesystem problem, but 2.2.8 wouldn't).
You're BOTH correct..somewhat
by
Sleepy
·
· Score: 1
I don't think the other guy was being unappreciative of Slashdot, and he's well within his rights to constructively criticize Slashdot (assuming Rob welcomes such comments, and I would guess he does). Remember Slashdot is a commercial website now... I'm sure those banner ads add up. If they're smart at/. they're also using the polls to generate refined profiles of this community.
A kernel filter would be nice, and it would also have been nice for this story to at least summerize what's new. There's no information here other than "new kernel". I guess I'll find out when I run buildkernel to tweak for the AMD K-6 450 I picked up at the computer show today..:-D
Re:Please stop posting devel kernel releases.I tot
by
Andreas+Bombe
·
· Score: 1
And there is a Slashbox that displays current stable and dev versions as seen on LinuxHQ...
I think we need (at least) 3 linux topics:
by
Rob_D_Clark
·
· Score: 2
1) linux, general 2) linux kernel, stable 3) linux kernel, unstable
This way folks can have the flexibility to filter out some/all/none of the linux related posts.
I agree with the previous poster about this. A Linux kernel slashbox would rock! Id have it as my first one listed, you could have a script that reports the current stable and devel kernels as links that would by default take you to linuxhq or something.
I like this idea, maybe even with some kind of discussions linked to the slashbox. That way the people who want to see what the latest kernel is on slashdot can and those who don't want to won't. I certainly like the idea better than having every devel release posted as a story.
--
-matt
How about a "software update" category?
by
scrytch
·
· Score: 1
Kernel updates could be tossed in with general software update notifications, stuff that isn't really big news, just YA update.
Maybe have a raw steak for an icon, as a reference to freshmeat
-- I've finally had it: until slashdot gets article moderation, I am not coming back.
No kidding. I was just about to download 2.2.8 when I realized that 2.3.2 was just released. Best advise, don't download it unless it has something necessary or something you REALLY want to mess with.
Slashdot has always announced the devel kernel releases. Please search Slashdot for "kernel 2.1 released", if you doubt this. Go on. There is a reason for the little "search" thing down there at the bottom of this page.
If you don't like an article, don't click "Read More". I really cannot see how this is difficult to comprehend.
Please stop whinging about a free service and let Rob and friends run their site as they please. Slashdot might not be the quickest place to report the releases, but it does give a good place to see discussion about problems others have had with the release. But obviously not this article, today.
POLL IDEA: devkernel announces?
by
nowonder
·
· Score: 4
as written wrt 2.3.1 i think only announcements should be made that feature a real news element. but thats only my opinion, so why not make a poll:
how would you like your kernels? * i want it all * no development kernels, please * kernels -> slashbox * let me filter them/new category * only important ones * medium with chili and sauce hollondaise
-- --
NoWonder of WonderWorks/OmegaProject
Re:POLL IDEA: devkernel announces?
by
dos+equis
·
· Score: 1
This is what I reckon: * Announce all stable kernels under topic 'Linux' * Announce all dev kernels under topic 'Linux Kernels' except when they are so fantastic that everybody wants to know about them. Then they too can be announced under topic 'Linux'
No, 2.3.x is a DEVELOPEMENT tree. It's not intended for general use. That's what 2.2.x is here for. The developement releases come out often and are not thoroughly debugged or tested. They often contain unknown and sometimes dangerous bugs.
The difference between 2.2.8 and 2.1.44 is 2.2.8 could cause problems under heavy I/O. I think 2.1.44 pretty much was just about garanteed to trash your fs.
The really short time between 2.2.8 and 2.2.9 was due to a nasty bug that could cause fs corruption. Other than that it's averaging about 1 every 2 weeks, not too bad. And remember just because there is a new kernel doesn't mean you have to upgrade. Unless the kernel does something for you specifically there is no need. Some of us (my self included) like to stay on the bleeding edge, but then again I don't complain about how fast they come out.
They can (and often are) quite unstable. Some of them (2.1.44 comes to mind) can even trash your file systems. Basically don't play with them unless you are willing to deal with your system being rendered useless.
I'm not saying that all kernel anouncements should be ignored. Just the devel ones. A) because newbies might get bitten. B) There are going to be a lot of them and it's quickly going to get very annoying, espeically when it gets to the point where there are 3 releases on the same page of slashdot.
They aren't relevant for most slashdot readers and there are going to be a LOT more of them before 2.4 comes out. Posting them to slashdot is just a waste of space.
I disagree. Slashdot has always been linux oriented, and I think kernel releases are a justified topic for posting. Slashdot is my portal. I don't go to any other portal site, as the news from slashdot pretty much takes care of anything I'd be interested in reading about. I don't want to go monitoring the kernel releases on some other site, but its nice to know when a new one is released.
Its not a big deal. I can live with it. And if I'm not mistaken... you can filter it out if you want. Adding a separate category for linux kernel releases might be a nice addition tho if you want to filter them THAT badly.
As I recall most, if not all of the 2.1 kernel releases were announced. There's at least a day, usually 2 or 3 between releases, so unless you have a LOT of headlines on your page, its unlikely you'll see more than one at a time.
As for newbies, I don't see this as a big deal. Assuming they're as unexperienced as you claim by the time they read enough documentation to get the kernel installed they should be able to understand that development releases are possibly unstable and potentially dangerous.
I knew about the existence of the driver before, but didn't want to use it until it hit some level of stability... I figured that if it had been included with the kernel now, it probably was worth trying out. (Unfortunately right now I'm getting kernel oopses galore from the driver.)
Besides, 2.3.2 is not too far out from 2.2, I'm not using any other experimental stuff (like USB), and my system's running fine otherwise.
No reason to be that scared. Backup anything important; if you are lazy and have lots of space, just backup the whole raw partition to somewhere else on the network. Then no matter how badly the kernel mangles your disk, it is very easy to return it to a known good state. The NTFS module is quite unstable; even read-only it has locked up solid (repeatably, so I should work on finding the bug, *sigh*). But I've never lost any data to it, and only a little time.
I realize that its not practical if you are low on disk space and don't have the luxury of a Sun server full of big disks nearby, but I often find myself using gzip and an rsh pipe to send an entire partition or disk over the network to a file server before attempting something questionable. (Heck, I occasionally reinstall Windows boxen that way:)
Also, it might be good to look into the history of the HPFS r/w code... if it is known to be relatively stable, and has just been waiting to be mainlined because of the feature freeze preceding 2.2, then I wouldn't be too nervous about using it. (I don't know in this case; not an OS/2 fan, personally.)
If you want to post on/. every time there's a new development kernel you'll just swamp yourself. There could be a new development kernel maybe several times a day, now just after the new development tree has been opened. Linus always starts with revamping things completely, and then he sends out new versions at a frenetic rate so that the other developers can fix their parts (in other words, those kernels might not even compile).
There IS a kernel version SlashBox...
by
Chris+Pimlott
·
· Score: 4
It's called "LinuxHQ Kernel Versions." Gives the current new and old versions of stable and development kernels, with links to the files and the patch browser.
I see, since you can't flood the comment section with dumb crap, it's Rob's perl scripts that are buggy. They're not buggy, he probably just never expected anybody to do anything so dumb. Maybe it's you that are buggy.
Bitkeeper? (or similar Source Management System)
by
C0sm1c
·
· Score: 1
Is the new development kernel going to use BitKeeper or some other similar source management system?
I've been wondering on this for a long time now , I heard Linus at least some of the other kernel developers were interested, what's the current status of such a move?
-- ---
C0sm1c
Re:Your perl scripts are buggy Rob!
by
skip277
·
· Score: 1
While this person is obviously an idiot troll, you have to respect the amount of work that went into this.:-)
Skippy
-- "False modesty is the refuge of the incompetent." - The Stainless Steel Rat
It seems that only yesterday that 2.3.1 came out. Actually it was;). I think we need to stop posting when every new kernel comes out. Anything in the development branch shouldn't be installed by anyone bu those who are doing development or like the bleeding edge and these people will find out that a new kernel is out through different channels anyway.
So, let's stop this madness; Slashdot is news for nerds, not Linux Patches and by the way did you hear that...
Those who need it will find it.
Why not just announce new kernel features?
by
Trojan
·
· Score: 1
Since there are hardly any postings about the kernel release itself, it seems obvious that certainly not all development kernel releases earn an announcement on Slashdot.
Nobody is really interested in talk about a bunch of updates. Software updates is what Freshmeat is for. Slashdot is for news.
Looking at the Changelog, it seems that the real news here is: Centaur C6 MCRs now supported. Does that deserve a Slashdot article? I think not.
Re:Why not just announce new kernel features?
by
Trojan
·
· Score: 1
I can't follow you.
Why would this have anything to do with Microsoft? This has to do with Slashdot and replies like yours.
FYI, I am running kernel 2.2.8 and will soon upgrade to either 2.2.9 or 2.3.2. But there are dozens of ways to find out about new kernel releases.
Snapshots of egcs are not discussed on Slashdot, so why should development kernel release be discussed.
Slashdot Mirror
They are work in progress and thinks might be buggy or broken in that process.
I totally agree with you. Please, Rob, don't post each and every update to 2.3.2... 2.1.x went up to over 130 before we hit 2.2, and considering there are only maybe 10 stories posted per day, let's not waste one or two of them on kernel updates that we can find out about many other places if we want to know.
I like them. Please keep them around.
I understand that people will want to filter them; maybe you can make a special type of story that is easily filterable.
That's exactly what it's good for. Have you seen a fully graphical, one-floppy linux install? You will.
(and no, I'm not counting Caldera 2.2 since it doesn't work in 99% of real-world installs)
No work.
banner -w 60 'Linux sucks!'
I'm sure, anybody who's interested in this have subscribed a linux-mailinglist or something like this or can read it on freshmeat.
I think that will work a lot better, keep the latest release announcements up there, and you can add/remove it if you desire.
...this is exactly what *BSD does, it's called *BSD-current. You can sup&install a new kernel every day if you want. You can even sup&make a new world every day if you want...
:-)
Like Linux devel kernels, *BSD-current ist not for the "average" and not guaranteed to be stable or working well (but in most cases it is!).
The only difference to linux is that *BSD doesn't change the kernel version every day.
I really like the idea of "current" and I think "bleeding edge" linux users would love this too.
Does kernel.org offer sup? I've browsed the website and only saw ftp and http. Why don't they support sup? It makes life much easier if you always want to have the latest sources.
Not just Debian. RH and SuSE are working on them as well.
The VGA 16 framebuffer is useful for anyone who
doesn't have a VESA compliant video card. VGA16
is likely to work on any VGA card.
Alan Cox was involved. He works for RH.
Hey all! Yeah, I noticed that, and I think it's GREAT! ;) And I'm still using it. (2.2.9) Works fine/great! h pfs/index-e.cgi
BUT! I do *NOT* think this is a reason to use 2.3. After all..
v2.0 and 2.2 already _*HAVE*_ a rw driver!
I have been wondering for QUITE a while why it wasn't included in 2.2, and I found out when I went to go d/l a newer version of the driver. It was rewritten at 2.1.13x, the very end of 2.1.x, so there was little (if any) chance for a major thing (ro-rw? Big!) to be included in 2.2. However, I d/l'd it, and installed it on 2.2. (2.2.0pre(Something) iirc.
So yeah, this is NOT a reason to use 2.3, however, since 2.3 recently branched, it MIGHT be okay to grab stuff out of 2.3 and replace the 2.2 stuff with it yourself, but I think the better idea is grabbing each individual driver, seeing what the author has to say about using it with 2.2, and replacing the current with it. The page for the hpfs (rw) driver is
Read-Write HPFS Driver for Linux, http://artax.karlin.mff.cuni.cz/~mikulas/vyplody/
So, go check it out! There's a chance that 2.3's is newer, but I REALLY doubt it! Hope I could've been of help!
(Actually, I posted a similar question on the 2.2.7 (or 6?) article, asking about the hpfs modifications in that 2.2.x)
- Ajay
To see how the (at least some) development community feels about SlashDots' posting stories about Devel kernels, do a search on Deja.com for "slashdot" in recent days.
Sorry about the AC post, at least the initials march.
AC
> A) because newbies might get bitten.
Thats part of being a linux newbie.
Sometimes you to live and learn.
I'm not suggesting newbies download
devel kernels, I'm just saying that
learning the hard way is not always bad.
You can really only speak for yourself.. I personally enjoy reading about updates. I still think it's a very good idea to make a different "topic" so that those who are not interested may filter away. Instead of using "Linux" and the penguin, how about "Linux Kernel Updates" -- any ideas for the picture? Maybe instead of constant bickering (not just on this topic, but on all topics by all people) maybe you can look at it from a different angle? Is there any good reason NOT to post something? No, just make it a new section and filter it. That way you only have to worry about it the first time it's posted - although if it's posted in the wrong topic, then... OH WELL that's another story ;) nuff rambing from me.
Posted Anonymously to avoid moderation from being undone.
Ahead of everyone else? Caldera's already gone to market with it.
Whatever.
Anyone experienced problems booting with a new kernel? I compiled 2.2.9 friday and when i boot i just see Uncompressing xxx ....... and i'm returned to the lilo prompt. 2.2.0-2.2.4 compiled and booted fine but 2.2.9 was compiled with a new egcs (1.1.2) and a new binutils (2.9.1.0.23). I really don't know what can be wrong? Maybe a problem with my egcs/binutils? But i compiled a lot of stuff with this like fileutils, sh-utils, textutils, util-linux, procps etc and all is working fine. There are 2 entries at my lilo.conf. linux for 2.2.9 and linux1 for 2.2.4.
TIA
Yes, Linus said basically that he's going to switch to Bitkeeper in the future. It just wasn't ready enough for the launch of the 2.3 series. I'm sure Larry McVoy and company are workind hard on it as we speak.
Well, that's just fine with me, this way bugs and 'features' are fixed quickly. If M$ did release bugfixes that fast most of us would be using NT.
There once was a lamer named Nermal
Who wanted a shiny new kernel
He did not use patch
So he clogged up the hatch
and caused many a ranting infernal
Why don't you use the Slashdot filtering capability?
If you think they are a waste of space (and time)
Then:
Don't click on articles pertaining to them
Don't post messages about them
Just ignore dev kernel release articles
Are the people who run slashdot under your pay?
I don't think so...
I know that there is a slashbox available for kernel releases already, the LinuxHQ box. How about expanding this box slightly, so like the poll slashbox, there is a link for people to post comments. The comments could be cleared after every new release.
In this way those that are interested in reading kernel anouncements have a handy single source of announcements and furthermore a forum to discuss them (yeah, I know the right place to discuss problems etc is on the kernel ml, but for other issues that aren't appropriate there).
I think most people will agree that they are a waste of space in the main news section, but there is definitely enough people to warrant there inclusion somewhere.
Opinions??
- 16 color VGA framebuffer console driver added.
So what exactly is this? Is this along the lines of a stripped down GUI for the console? (obviously not something to the extent of an X server.) I'm guessing a use for it would be akin to Win95's install, where it dumps to a low color GUI for the entire thing. Anyone care to shed some light on this?(sorry for the AC post, as moderating the thread from evildoers and for insightful users prevented me from posting )
Those people who don't like to have to look at the small title and articles for new realease of kernels don't have too. I might be the only one, but if you sign in and goto prefrences you can select what articles see or don't see. I use this so I don't have to read all the damn star wars articles.
I'm expecting to see the development kernel numbers climb pretty rapidly.. Probably a new one every day, with the occasional twice-a-day ones and the occasional skipped day.
Perhaps Rob/Hemos/someone can make a special 'Kernel' or 'Kernel-Development' news type that people can filter out. I'd actually recommend both types. That way, normal people can hear about the fixes to the stable end of things, and the people that love the bleeding edge can go out and grab the devel kernel..
Of course, I'm sure someone could just write a nifty script that fingers linux.kernel.org to update that stuff automatically (or maybe a slashbox.. hmm..)
On one hand, I enjoy reading Slashdot discussions of the new Linux kernels. Success/failure reports are good, as are discussions of new features of kernels. A Slashbox, while good for announcing them and keeping up with the latest, wouldn't allow that discussion.
But please only announce development kernels when there is some REAL news. Like when USB is mostly working, or when the journaling FS is added.
Just my $0.03,
Micah
How about a kernel of corn?
- A.P.
--
"One World, One Web, One Program" - Microsoft Promotional Ad
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
The latter is obviously a greater waste of bandwidth. It contains zero useful information, whereas the former contains the information that there is, in fact, a new kernel out. The signal-to-noise ratio of the news about the kernel updates, however low, is therefore infinitely higher than that of the whiners, which is zero.
Posted by d106ene5:
Kernels are great!
Kernels are good!
Not everyone untars them,
but everybody should!
Get it installed!
Find where it breaks!
Your system is broken,
forget about Quake!
Can we all stop whining? There are only a small number of types of whines, and if you see it once, please don't post the same stuff again. If you want to add more, post to the original whine. I'm sick of shorting through all this shit. I miss the days when people would put up their questions and stories about their experiences with a new version.
>Looking at the Changelog, it seems that the real news here is: Centaur C6 MCRs now supported. Does that deserve a Slashdot article? I think not.
Of course you Mircosoft flacks would think this because posting a "bunch of kernel updates" as you losers express it on Slashdot exposes the lies (See the Mircosoft "Linux Challenge" WWW page for an example of this) that the Mircosoft PR department and it's allies try to spread about Linux for all the world to see.
How? Filter out everything relating to Linux? A "Linux Kernel" category would be nice. I can't imagine what the icon for it would be. But really, unless there's something significant about a new kernel, I don't see why it needs to be posted. Especially since the hackers are in the development tree now, and kernels are going to be popping up once every few days.
If you ever want to see the data on that HPFS partition again, don't. Using a development kernel, you're assuming that you will lose all your data. Be careful.
How about a /box that shows what the current dev
and stable kernels are? That would save the postings...
Linux Kernel
------------ Stable: 2.2.9 (5 comments) Development: 2.3.2 (2 comments)
With a new slashdot forum automatically created for new kernel releases, in case people want to discuss them. Obviously only important new releases should get a mention in the `main' slashdot. Perhaps only post if a new release is seen as a major milestone, or if it contains fixes for a major data loss/security problem (e.g. 2.2.0 would have been announced. 2.2.9 would probably get a mention because of the filesystem problem, but 2.2.8 wouldn't).
I don't think the other guy was being unappreciative of Slashdot, and he's well within his rights to constructively criticize Slashdot (assuming Rob welcomes such comments, and I would guess he does). Remember Slashdot is a commercial website now... I'm sure those banner ads add up. If they're smart at /. they're also using the polls to generate refined profiles of this community.
:-D
A kernel filter would be nice, and it would also have been nice for this story to at least summerize what's new. There's no information here other than "new kernel". I guess I'll find out when I run buildkernel to tweak for the AMD K-6 450 I picked up at the computer show today..
And there is a Slashbox that displays current stable and dev versions as seen on LinuxHQ...
1) linux, general
2) linux kernel, stable
3) linux kernel, unstable
This way folks can have the flexibility to filter out some/all/none of the linux related posts.
--Rob
I agree with the previous poster about this. A Linux kernel slashbox would rock! Id have it as my first one listed, you could have a script that reports the current stable and devel kernels as links that would by default take you to linuxhq or something.
v2sw7CUPhw5ln6pr5Pck4ma7u7LFw0m6g/l7Di5e6t5Ab6TH.
Kernel updates could be tossed in with general software update notifications, stuff that isn't really big news, just YA update.
Maybe have a raw steak for an icon, as a reference to freshmeat
I've finally had it: until slashdot gets article moderation, I am not coming back.
No kidding. I was just about to download 2.2.8 when I realized that 2.3.2 was just released. Best advise, don't download it unless it has something necessary or something you REALLY want to mess with.
~centurion
Anybody notice that linuxhq.org has a rather...interesting...top page?
Christ, I wish the script kiddies would all just dry up and blow away.
Slashdot has always announced the devel kernel releases. Please search Slashdot for "kernel 2.1 released", if you doubt this. Go on. There is a reason for the little "search" thing down there at the bottom of this page.
If you don't like an article, don't click "Read More". I really cannot see how this is difficult to comprehend.
Please stop whinging about a free service and let Rob and friends run their site as they please. Slashdot might not be the quickest place to report the releases, but it does give a good place to see discussion about problems others have had with the release. But obviously not this article, today.
as written wrt 2.3.1 i think only announcements
should be made that feature a real news
element. but thats only my opinion, so why not
make a poll:
how would you like your kernels?
* i want it all
* no development kernels, please
* kernels -> slashbox
* let me filter them/new category
* only important ones
* medium with chili and sauce hollondaise
-- NoWonder of WonderWorks/OmegaProject
No, 2.3.x is a DEVELOPEMENT tree. It's not intended for general use. That's what 2.2.x is here for. The developement releases come out often and are not thoroughly debugged or tested. They often contain unknown and sometimes dangerous bugs.
-matt
The difference between 2.2.8 and 2.1.44 is 2.2.8 could cause problems under heavy I/O. I think 2.1.44 pretty much was just about garanteed to trash your fs.
-matt
The really short time between 2.2.8 and 2.2.9 was due to a nasty bug that could cause fs corruption. Other than that it's averaging about 1 every 2 weeks, not too bad. And remember just because there is a new kernel doesn't mean you have to upgrade. Unless the kernel does something for you specifically there is no need. Some of us (my self included) like to stay on the bleeding edge, but then again I don't complain about how fast they come out.
-matt
They can (and often are) quite unstable. Some of them (2.1.44 comes to mind) can even trash your file systems. Basically don't play with them unless you are willing to deal with your system being rendered useless.
-matt
I'm not saying that all kernel anouncements should be ignored. Just the devel ones. A) because newbies might get bitten. B) There are going to be a lot of them and it's quickly going to get very annoying, espeically when it gets to the point where there are 3 releases on the same page of slashdot.
-matt
They aren't relevant for most slashdot readers and there are going to be a LOT more of them before 2.4 comes out. Posting them to slashdot is just a waste of space.
-matt
I knew about the existence of the driver before, but didn't want to use it until it hit some level of stability... I figured that if it had been included with the kernel now, it probably was worth trying out. (Unfortunately right now I'm getting kernel oopses galore from the driver.)
Besides, 2.3.2 is not too far out from 2.2, I'm not using any other experimental stuff (like USB), and my system's running fine otherwise.
Finally, I can write to my OS/2 drives...
I hadn't planned to install a 2.3.x kernel this early, but I guess I'll do it for that feature by itself...
If you want to post on /. every time there's a new development kernel you'll just swamp yourself. There could be a new development kernel maybe several times a day, now just after the new development tree has been opened. Linus always starts with revamping things completely, and then he sends out new versions at a frenetic rate so that the other developers can fix their parts (in other words, those kernels might not even compile).
It's called "LinuxHQ Kernel Versions." Gives the current new and old versions of stable and development kernels, with links to the files and the patch browser.
Happy?
-----BEGIN ANNOYING SIG BLOCK-----
Evan
rooooar
Yeah, except 2.2 is also coming out fast. Observe:
-rw-r--r-- 1 ftp ftp 13497506 Mar 28 22:54 linux-2.2.5.tar.gz
-rw-r--r-- 1 ftp ftp 13588897 Apr 16 14:46 linux-2.2.6.tar.gz
-rw-r--r-- 1 ftp ftp 13677325 Apr 28 11:42 linux-2.2.7.tar.gz
-rw-r--r-- 1 ftp ftp 13808890 May 11 12:59 linux-2.2.8.tar.gz
-rw-r--r-- 1 ftp ftp 13827947 May 13 16:54 linux-2.2.9.tar.gz
-Chris
what realy is the problem with dev kernels?
I like beans, and you?
Is the new development kernel going to use BitKeeper or some other similar source management system?
I've been wondering on this for a long time now , I heard Linus at least some of the other kernel developers were interested, what's the current status of such a move?
--- C0sm1c
While this person is obviously an idiot troll, you have to respect the amount of work that went into this. :-)
Skippy
"False modesty is the refuge of the incompetent." - The Stainless Steel Rat
We got that open your eyes, just check "LinuxHQ Kenrel Versions" and voilá
De lyckliga slavarna är frihetens bittraste fiender, legalisera!!!
i find it interesting to hear about the new kernals. so there :p
besides, like it's affecting you.
It seems that only yesterday that 2.3.1 came out. Actually it was ;). I think we need to stop posting when every new kernel comes out. Anything in the development branch shouldn't be installed by anyone bu those who are doing development or like the bleeding edge and these people will find out that a new kernel is out through different channels anyway.
So, let's stop this madness; Slashdot is news for nerds, not Linux Patches and by the way did you hear that...
Those who need it will find it.
Since there are hardly any postings about the kernel release itself, it seems obvious that certainly not all development kernel releases earn an announcement on Slashdot.
Nobody is really interested in talk about a bunch of updates. Software updates is what Freshmeat is for. Slashdot is for news.
Looking at the Changelog, it seems that the real news here is: Centaur C6 MCRs now supported. Does that deserve a Slashdot article? I think not.