Announcing: Slashdot Deals - Explore geek apps, games, gadgets and more. (what is this?)

Thank you!

We are sorry to see you leave - Beta is different and we value the time you took to try it out. Before you decide to go, please take a look at some value-adds for Beta and learn more about it. Thank you for reading Slashdot, and for making the site better!

Linux 2.2.0pre5

justin++ posted about 16 years ago | from the test-me,-it-calls! dept.

Linux 97

Linus released 2.2.0pr.5 this afternoon. Hopefully, enough mirrors will have synced by now. People need to test these babies so the real 2.2.0 is as close to bug-free as possible.

Sorry! There are no comments related to the filter you selected.

hmm... patch? (0)

Anonymous Coward | about 16 years ago | (#2047072)

Ok, so like a good Slashdot lemming (grin), I jumped onto ftp.us.kernel.org, and grabbed the 145k PATCH instead of the full blown 10meg kernel. I have pre4, so just how do I go about applying this patch?

(I'm trying to learn, anyway)

hmm... patch? (0)

Anonymous Coward | about 16 years ago | (#2047073)

No need to apologize but...
RTFM. It includes docs.
(Thanks for saving bandwith for those who need it tho, I wish the losers with T1s would be so considerate).

(Not the OS)

Patching... (0)

Anonymous Coward | about 16 years ago | (#2047074)

To patch from 2.2.0-pre4 to pre5 simply do:
cd /usr/src/linux
patch -p1 [path_to_patch_here]

Patches can also be removed by doing:
patch -p1 -R
And, just fyi, Alan has put up a patch for pre5-ac1. I don't know what it contains but I assume it's good so I applied right away!

Nothing beats the Sex Sells Ads on /. (0)

Anonymous Coward | about 16 years ago | (#2047075)

Thanks SurfFree.com! I'll make sure to never do business with you, as long as you have lame bikini clad women to sell lame internet access.

Man, pre4 is still compiling... (0)

Anonymous Coward | about 16 years ago | (#2047076)

...and now there's pre5. Yeesh. I'm goin' to Hawaii until the dust settles...

Where... (0)

Anonymous Coward | about 16 years ago | (#2047077)

... has the CHANGES-file gone?

when to final 2.2? (0)

Anonymous Coward | about 16 years ago | (#2047078)

Have you tried this version? It may work just fine for you.


Debian? (0)

Anonymous Coward | about 16 years ago | (#2047079)

So does this mean Debian 2.1 will be released soon? :-)

rpms? (0)

Anonymous Coward | about 16 years ago | (#2047080)

Where can I get RPMs for Redhat Linux 5.2 of the Linux 2.2.0 pre-releases?

Debian? (0)

Anonymous Coward | about 16 years ago | (#2047081)

You don't have to wait for release to use the vast majority of it. I have been running slink for months. The nice thing is that the devel kernels drop right in!

As for when slink gets released, as soon as Debian wises up and stops creating a new unstable tree before the previous one is released. Could you imaging Linus starting 2.3 before 2.2 was out? 2.2 would NEVER get done because everyone jumps ship to work on the newest version.

That is just plain dumb and is what causes Debian to lag.

rpms? (0)

Anonymous Coward | about 16 years ago | (#2047082)

i've compiled kernels myself before (especially when I used slackware) but I find rpms to be a much more convenient and organized way of doing things


Anonymous Coward | about 16 years ago | (#2047083)

when i compile, it has problems in the net/ipv4 directory with an undefined symbol IP_MASQ_F_DLOOSE.

Yet another non-2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047084)

I'm starting to wonder when we'll see 2.2.0pre115. :-)

Seriously, it's great that there's so much focus on debugging. Microsoft would never put off releasing a product due to so few bugs.

Yet another non-2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047085)

Ofcourse Microsoft wouldn't put off releasing a product with so few bugs, as they wouldn't even manage to make a program with so few bugs..

No Hurry on the 2.2 (0)

Anonymous Coward | about 16 years ago | (#2047086)

Take your time save the good name for a perfect kernel, if people really want a new kernel they should get the pre-releases (I just can't wait for the 2.3 series).


thanks (0)

Anonymous Coward | about 16 years ago | (#2047087)

I should be able to mold this rpm for 2.1.133 into one for 2.2.0pre5

diminishing returns? (0)

Anonymous Coward | about 16 years ago | (#2047088)

While I agree that those who are coding should take the time to make it meet their personal standards, aren't they approaching the point of diminishing return. Aren't you gonna keep finding bugs as long as you keep working on it? I'm pretty sure there is gonna be a 2.2.1 less than 48hrs after the release of 2.2 anyway. I'd say it's closing in on time to either shit or get off the pot... but I'm not Linus so what I think doesn't matter now does it ;)

No ISDN in 2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047089)

ISDN = Integrated Services Digital Network
It's a sort of high speed telephone line (64k/128k), which is used a lot in germany and the netherlands

Mousewheel stopped working (0)

Anonymous Coward | about 16 years ago | (#2047090)

Are there any more people whos mousewheel doesn't
work anymore with the newer kernels?

No ISDN in 2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047091)

Linus sucks if he does that...
I live in .nl, and i have isdn too...
I think he's ignoring millions of (potential) linux users here...

No ISDN in 2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047092)

..and in Norway and Sweden.

Almost three times faster compiling! (0)

Anonymous Coward | about 16 years ago | (#2047093)

Good grief!

(This is the Slack3.4-usin' anon coward who's too lazy to log in.)

2.2.0pre4 compile under 2.0.36: 7m30s
2.2.0pre4 compile under 2.2.0pre4: 5m16s
2.2.0pre5 compile under 2.2.0pre5: 2m40s

It's like I've got a whole new computer! (And yes, before anyone asks, I did each compile with a freshly unpacked tarball).

Your mileage may vary. I see from the kernel mailing list that there have been huge improvements to the virtual memory management in just the last few days. Probably your speed increase depends on how much RAM you have - I have 64MB.

SuSE will do the job (0)

Anonymous Coward | about 16 years ago | (#2047094)

...just as they did with 2.0.x.

I guess they will offer customized kernels which are already patches for ISDN users.
In Europe, SuSE is the only way to go anyway, if you want no hassle (well, perhaps DLD, too, if you know German).

In a survey by a German Internet mag about twice as many people used ISDN compared to modems, so ISDN users can't be ignored.

Linus is right if he does that; his job is to sort out code that is immature or improperly maintained. So this will probably help us to get a better (coordinated) ISDN support.

No ISDN in 2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047095)


Have some faith in the Linux community. Although it is not in the mainstream kernel 2.2.0, it probable is in 2.2.x (x>0).

patch -s (0)

Anonymous Coward | about 16 years ago | (#2047096)

The patch program has a useful option '-s':

bunzip2 -c ../patch-2.2.0-pre4.bz2 | patch -s -p1

Will keep patch silent about all it's activities and only inform you of problems (like rejects). There's no need to see all those correct patches applied, and you get an instant view of what went wrong (usually nothing).

Happy Patching,

--Tim :-)

No ISDN in 2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047097)

and Finland...

No ISDN in 2.2.0 (0)

Anonymous Coward | about 16 years ago | (#2047098)

What he means is that the version of the ISDN subsystem included in 2.2.0 sucks rocks, because the ISDN team thought that last year's "code slush" was a full code freeze and stopped sending patches to Linus.

We'll probably get a working ISDN fairly soon, though, as the patches exist, but are too big to be put into 2.2.0 at this late date (accoring to Linus).

BJH (who's forgotten his password AGAIN...)

This must be me, it can't be the kernel... (0)

Anonymous Coward | about 16 years ago | (#2047099)

But I never noticed this before:

Jan 7 06:43:28 bastard pppd[566]: Using interface ppp0
Jan 7 06:43:28 bastard pppd[566]: Connect: ppp0 /dev/ttyS0
Jan 7 06:43:31 bastard modprobe: can't locate module ppp-compress-21
Jan 7 06:43:31 bastard modprobe: can't locate module ppp-compress-26
Jan 7 06:43:31 bastard modprobe: can't locate module ppp-compress-24
Jan 7 06:43:35 bastard pppd[566]: local IP address 206.170.x.x
Jan 7 06:43:35 bastard pppd[566]: remote IP address 209.233.x.x

Wuzzat? Yes, it does work, but I have no clue how to make modprobe happy. I'm using kmod, by the way.

Oh, well... (0)

Anonymous Coward | about 16 years ago | (#2047100)

As soon as ISDN costs less than $450 a month to keep nailed-up, I'll care. (And don't nobody whine to me about Centrex ISDN!)

Meanwhile, I'll just keep saving up for 384 SDSL -- at half the monthly cost, and without requiring kernel modifications.

Why is it nessessary for 2.2.0 to be released soon (0)

Anonymous Coward | about 16 years ago | (#2047101)

until your power decides to go out. :-)

That usually takes a few years.

But.... hmmm.... I betcha I'd have great uptime!

Ummm... no. (0)

Anonymous Coward | about 16 years ago | (#2047102)

(Don't worry, I'll flame him)

All you people clamoring for a final release -- are you building and testing the prereleases? No? Holding out for 2.2.0 final, are ya? Well, put your money where your mouth is.

If you want it to be final, get in there and test it. Submit IRs to the kernel list, exercise it, enjoy it. It *is* final, except for bug fixes. It's the same damned thing. You can go ahead and call it final now, and then splat out a whole bunch of post-release patches, or you can live with pre.

I'd rather the .0 version be as bug-free as possible (in contrast to 2.0.0) -- this time there are plenty of media pundits to razz us if it doesn't look mighty good.

Bug reports ? (0)

Anonymous Coward | about 16 years ago | (#2047103)

Does one now were to get a list of current kernel already reported bugs, and where to report bugs ?

Because 2.2.0pre5 compilation fails with some masquerading options, for a trivial reason (I think): one constant have wasn't #define-d. I expect that this bug had been instantly reported and that trivial manual fix reported.

Debian? (0)

Anonymous Coward | about 16 years ago | (#2047104)

I asked the question about the 2.2 kernel and debian and received the following mail:
Slink is "frozen". That means only bugfixes get in, no new improvements. This applies to kernels as well as applications.
So 2.2.0 won't likely be in slink. It may appear in the next version (potato) if it is released while that one is still "unstable".
So far the "DEBIAN O-ton". I thing this sounds funny DEBIAN 2.2 with LINUX-Kernel 2.2

cu l8er

diminishing returns? (0)

Anonymous Coward | about 16 years ago | (#2047105)

Don't bother I have my asbestos underwear on =) Seriously though, I have downloaded, compiled, and tested all the 2.2pre's. They work great for the hardware I use and the projects I work on at home. I don't guess I understand how 2.2 becomes "finished", other than Linus says so... Seems like a very subjective matter, as there are always going to be some bugs that we don't find soon enough. How many is too many? I'm not saying it should be released immediately, I'm just saying that the sooner it's released the sooner it will get mass testing, and stabalize enough to use on my production boxes at work. Other than work I don't care how long it takes...

not only that...it's an NT isp! (0)

Anonymous Coward | about 16 years ago | (#2047106)

No joke. I checked em out once expecting a nice inexpensive nationwide unix isp, but found they run a bunch of MS junk for their servers. This is NOT the sort of thing Rob should be advertising... *sigh*

Fortunately, ad.blm.net resolves to an address on the dummy0 interface on my machine. :) Same thing with every other banner site I find. I suppose someday I'll have to get junkbuster if advertisers get smart and put the ads on the same hosts as content, but right now this works fine.

And no, you stupid whiners, I'm not ``stealing'' from Rob; I'm avaoiding having my (*very limited*! shared 28.8) bandwidth stolen by crap I don't care to see.

- RF (dfelker@cnu.edu)

Where... (0)

Anonymous Coward | about 16 years ago | (#2047107)

Ok, now tell us where to go if we don't want to read the patch file, and trace the coding changes back to what they change.

Please don't tell me that patches get accepted into the kernel with no comments about what they fix or change. Where is a copy of the list of comments about the changes made in this patch? I want something along the lines of

- fixed bug in sched.c which would occasionally leave a runable process idle even when the processor wasn't busy
- fixed a problem with buslogic scsi cards that could in very rare circumstances block the processor in a busy-loop for 30 seconds

and so forth.

This must be me, it can't be the kernel... (0)

Anonymous Coward | about 16 years ago | (#2047108)

ppp-compress-21 and ppp-compress-26 are aliases for bsd_comp and ppp_deflate. ppp-compress-24 must be also some alias.

just append these aliases to /etc/conf.modules
(i think there is a note in the ppp docs on how to do it right)

nothing is ever finished.. (0)

Anonymous Coward | about 16 years ago | (#2047109)

wow...why not read his comment again. He was actually saying what you are saying: that everything can be imrpoved and that any future "finished os" is a fictional future os.

vga consoles (0)

Anonymous Coward | about 16 years ago | (#2047110)

VGA console's not a problem at all. When you add the framebuffer... Then I have a problem.

Could someone please explain why there's no configuration to have the framebuffer without the bootpenguin? And would someone please tell me the scrolling bug that causes the penguin to eat my scrollback buffer and dmesg data while loading back in 2.1.125 has been fixed?


vga consoles (0)

Anonymous Coward | about 16 years ago | (#2047111)

I love the fbcon with matroxfb acceleration. 32 bit color at 1024x768, fonts look great, 8000 lines of scrollback (!).

The best part is that I can watch fbtv in the corner of the screen while working at the console.


It works for me (0)

Anonymous Coward | about 16 years ago | (#2047112)

It's a Logitech PS/2 mouse. It works fine with the 2.1.125
kernel but not with any newer kernels.

Why is it nessessary for 2.2.0 to be released soon (0)

Anonymous Coward | about 16 years ago | (#2047113)

So, what do you think of making a kernel module that will load a kernel, decompress it, shift memory pointers under the control of the new kernel, shift the stack pointers to the new kernel (including its own return pointer), and then de-allocate the old kernel?

Admittedly, it would only work for minor changes; too major a change could prevent it from working. However, it could help reduce the number of reboots, especially in the development side...

*heh*. Just think what that would do to one's uptime. (It'd raise my record from something like 21 days to many months, I'd guess. Especially since I'm currently implementing a hardware freeze on my box.)

Nothing beats the Sex Sells Ads on /. (0)

Anonymous Coward | about 16 years ago | (#2047114)

or better yet, lynx ;)

rpms? (0)

Anonymous Coward | about 16 years ago | (#2047115)

Perhaps what we really need is an FAQ on how to upgrade RH 5.2 to use the 2.2.0-preX series. Plus a set of rpms for the supplemental packages needed, like the modules stuff. I've seen most of this on the kernel site, but not in a terribly concise form.

This must be me, it can't be the kernel... (0)

Anonymous Coward | about 16 years ago | (#2047116)

Just add the lines

alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate

to your /etc/conf.modules file.

If this doesn't fix it be sure you've compiled and installed modules.


diminishing returns? (0)

Anonymous Coward | about 16 years ago | (#2047117)

I guess my problem with the 2.2.0pre kernels is that many people are afraid to try out a kernel (myself included) that is not labeled as "stable." There's only so much testing that can be done with prerelease and dev kernels before it his the massive amounts of people using the stable ones. I think we'd be better off with releasing 2.2.0 now and fixing the bugs after a much larger user base has tried it out.

Upgrading Redhat 5.2 / Cyrix M1 (old stepping) (0)

Anonymous Coward | about 16 years ago | (#2047118)

I presume this won't break 5.2 with 2.0.x kernels... Was the modutils package in RPM format, and where did you get it.

Plus I have a rather old stepping Cyrix P150 (M1). Am I SOL for running 2.2.0-0.5? Is this on someone's list to fix, or is this CPU being abandoned. Elsewhere in this tree, someone claims that old M1s don't work even if you call them i386 or i486.

Upgrading Redhat 5.2 (stock modutils is fine) (0)

Anonymous Coward | about 16 years ago | (#2047119)

While the RH5.2 modutils are not the latest, they seem to be perfectly fine for building and using 2.2pre kernels (at least, I'm still using the stock RH5.2 modutils 2.1.85 pkg; I figure that many RH users will have this config, so I'm testing the pre-kernels with the same config)

BTW. I got into building 2.1.xxx kernels fairly late (had previously just rebuilt 2.0.35 kernels), and I have to say, it is fun! Please, anyone who is a programmer, and interested in how operating systems work, build the kernels; look through the source code at the OS internals, it is VERY informative and a great educational tool.

PS. Also learned CVS very recently, and now, I don't know how I'd live without it. I do cross platform development, and it makes life much easier. So, again, I encourage developers to look into and use the tools of the free/open software movement. They are truly revolutionary (IMO).

Re: faster compiling!(1024HZ scheduler prob?) (0)

Anonymous Coward | about 16 years ago | (#2047120)

The "jiffies" counter is 32 bits on Intel, and gets incremented with each timer tick (ie. at 100Hz, by default). This gives roughly:

(2^32) / (100 * 60 * 60 * 24) ~ 1.3 years

before overflow. Alpha has 64 bit counter, so overflow just shouldn't occur.

Now, by changing to 1024Hz on Intel i386 processor, overflow occurs in:

(2^32) / (1024 * 60 * 60 * 24) ~ 49 days

So, does anyone know what happens to the machine when jiffies overflows? I assume it is not handled very gracefully (but I haven't checked, and the source doesn't seem to say, at first glance). Should be fun to check.

So, those who opt for a 1024 HZ value, beware...

Chad Netzer

download 2.2-pre5 here (0)

Anonymous Coward | about 16 years ago | (#2047121)

get patches here [sinister.com] .

Who needs kernel support!? (0)

Anonymous Coward | about 16 years ago | (#2047122)

I've got ISDN and pay about $80/month due to needing a repeater ($24/month) and do dial on demand to my ISP just fine. No per-minute charges. What I don't understand is who needs kernel support for ISDN? I've got an ISDN router and before that had a bitsurfr pro. Neither needed any drivers in the kernel to work.

No ISDN in 2.2.0 (1)

Erich (151) | about 16 years ago | (#2047123)

Then stick with 2.0.X or 2.1.X.

I don't plan on changing to 2.2.x untill I find a feature I need.

vga consoles (1)

stevied (169) | about 16 years ago | (#2047124)

vga consoles? I guess you mean framebuffer consoles. I imagine people whose machines don't implement any sort of text mode find them quite useful :) And if you have a PC and don't like framebuffer, don't use it..

It's a nice day... (1)

Luis Casillas (276) | about 16 years ago | (#2047125)

...when I manage to get it before Slashdot announces it :-)


hmm... patch? (1)

Luis Casillas (276) | about 16 years ago | (#2047126)

Do it this way. Say you keep your patches on /usr/src/, and your kernel is on usr/src/linux-2.2.0pre4/

First, patch it.

# cd /usr/src/linux-2.2.0pre4
# bunzip2 -c ../patch-2.2.0pre5.bz2 |patch -p1

Then, check for failed patches (files with a .rej extension):

# find . -name '*.rej'

If none appear, then the patch was successful. You can remove the original files that the patch saved (those with a .orig extension):

# find . -name '*.orig' -exec rm -f {} \;

Usually it's a lot easier, since scripts/patch-kernel (go and read it with less) under the kernel tree is a script that automatically applies a set of patches to a kernel tree. Sadly, the irregular numbering on the pre-2.2 series has broken this script (last time I checked)


Not this time!!! (1)

Luis Casillas (276) | about 16 years ago | (#2047127)

This is usually the case with pre-patches. But not with the official pre2.2 kernel patches Linus is putting out now.

It does apply to the ac patches, AFAIK (haven't tried them).


Wrong. (1)

HoserHead (599) | about 16 years ago | (#2047128)

Linus' 2.2 pre-patches are not cumulative, they're incremental, meaning you DO NOT remove pre4 to get pre5.

vga consoles - Necessary in the future (1)

Falathar (930) | about 16 years ago | (#2047129)

Actually, it's possible that you'd never see it. And therefore never be able to see whats going wrong if something bad happens. At least that's the way it works now with Plug and Pray monitors.

hmm... patch? (1)

Phaid (938) | about 16 years ago | (#2047130)

An amusing trick that is quicker than uncompressing and running patch manually:

# cd /usr/src/linux
# cp patch-2.2.0-pre5.bz2 patch-2.2.1.bz2
# ./scripts/patch-kernel

Current kernel version is 2.2.0-pre4
Applying patch 2.2.1 (bz2)

(You have to rename the patch file as the patch-kernel script doesn't recognize the -pre5 extension. Obviously this has no actual effect on the patch itself).

Nothing beats the Sex Sells Ads on /. (1)

sterwill (972) | about 16 years ago | (#2047131)

Ads? On Slashdot? Oh yeah... www.junkbusters.com. :)

No ISDN in 2.2.0 (1)

GeeWiz (1335) | about 16 years ago | (#2047132)

If there won't be ISDN support in 2.2.0 because Linus refuses [lwn.net] to include the lately sent-in patch file, this kernel version won't be quite useful here in highly-using-ISDN-Germany... :-(

Regards, Jochen

Problem Compiling? (1)

Foxpaw (1561) | about 16 years ago | (#2047133)

Has anyone else had a problem compiling this one? When I try and compile, it dies with this:

checksum.c:200: redefinition of `csum_partial_copy'
checksum.c:105: `csum_partial_copy' previously defined here.

Now, I know a little bit about programming, so I opened up checksum.c (which is in /arch/i386/lib) and checked out lines 200 and 105. They're function declarations. Line 200 declares function "csum_partial_copy", and line 105 declares function "csum_partial_copy_fromuser". So why does the compiler think that its trying to redefine "csum_partial_copy"?

I'm trying to compile under RedHat 5.2 using gcc-

No ISDN in 2.2.0 (1)

mill (1634) | about 16 years ago | (#2047134)

Don't blame Linus for this. If the ISDN people want it included in the kernel they better submit patches way earlier. The same happened to knfsd and now people are taking responsibility and knfsd has an official maintainer. Just needed a kick in the behind from Linus, I guess.


Pre-releases are good (1)

jd (1658) | about 16 years ago | (#2047135)

IMHO, moving from 2.1 to 2.2..0 pre gives bug-testing a whole new boost, which should help iron out a lot of last-minute glitches. (I remember having to wait, with 2.0 - I was able to use almost every development kernel prior to it without problems, but 2.0.0 simply wouldn't work.)

I'm not going to worry, no matter how long it takes. Weeeeell, if we get up to 2.2.0-pre150 I might wonder if maybe Linus switched to the pre phase a tad early.... :)

Why I'd like to use RPM's for prereleases (1)

Chuck Milam (1998) | about 16 years ago | (#2047136)

I like RPM because it allows me to keep track of files on my system, provides a powerful versioning system for up/downgrades, and most importantly, it saves time...

I'm pushing for a major switch from Solaris to RedHat Linux here at work. My major selling point is reduced administration time through the use of RPM.

Remember that RPM != Precompiled Binary. SRPMS allow you to compile from pristine source, but also give you the ability to track/update/remove every file created through the compilation process. I like that a lot better than the ".tar.[gz|bz2|Z]" system of spraying and orphaning files all over my file systems.

when to final 2.2? (1)

Millennium (2451) | about 16 years ago | (#2047137)

Whenever it's ready. Probably soon, however; I'd say it certainly wouldn't be more than two months away, and probably no more than one month.

IP Aliasing broken (1)

Tor (2685) | about 16 years ago | (#2047138)

It seems that IP aliasing is not working in the late 2.1 and pre-2.2 kernels.

Running the following command under 2.0.36 (and other 2.0 kernels) works fine:
ifconfig eth0:0

However, with the 2.2.0-pre5 kernel, this has no effect. I have built both Network aliasing and "IP: Aliasing" into the kernel.

Before I submit this as a bug, does anyone know if there is some new syntax or other requirement for this to work? E.g. some /proc/sys/net/ipv4 stuff?

WRONG: No ISDN in 2.2.0 (1)

John Goerzen (2781) | about 16 years ago | (#2047139)

Umm, did you even read the post you linked to at http://lwn.net/1999/0107/a/lt-isdn.html? It's not Linus's fault; he's doing what he should. Kick the ISDN4Linux people instead. Geez.

vga consoles - Necessary in the future (1)

logicTrAp (2864) | about 16 years ago | (#2047140)

The Frame buffer console was ported over to x86 because the PC98 spec no longer requires a text mode on video cards - so, in the future, it might be impossible to use Linux on x86 w/o a frame buffer console. As others have said, in the mean time, if you don't like it, don't use it.

Why I'd like to use RPM's for prereleases (1)

Prothonotar (3324) | about 16 years ago | (#2047141)

Well you're right: I like SRPMs too, but you know what an SRPM is? It's a tar.gz file (maybe a few), together with patches and a spec file.

When you install an SRPM, all it does is copy the tar.gz file(s) and patches to /usr/src/redhat/SOURCES and the spec file to /usr/src/redhat/SPECS (talk about splaying all over your filesystem...and why are the RPMS binaries a part of the /usr/src tree?). You have to then use the spec file to build the RPM, then install the RPM.

The problem is that if you're looking for someone to provide an SRPM for a kernel, then simply build an RPM from their spec file, you *still* have no control over the kernel configuration, which is pretty important when testing the kernel (which is, after all, what the prereleases are for).

If you're building your own RPM/SRPM, you haven't saved any time (especially considering that you often have to build the stuff successfully more than once if you are making your own spec file; once by hand [using the tar.gz] and again from the spec-- for instance to find out what files it provides).

I don't think the original poster cared (or knew) about building his own RPM, he was more concerned with just getting a binary package and installing it, letting others compile for him.

If you want to build your own RPM/SRPM, then just grab a spec file from an earlier kernel SRPM and hack...er, edit it to work with the new kernel. The steps are the same, more or less, only the configuration file (which you would presumably include preconfigured) will be different.
Aaron Gaudio
"The fool finds ignorance all around him.

Err....no modules? (1)

Prothonotar (3324) | about 16 years ago | (#2047142)

Don't you use modules? or is that why you have to make bzImage? Nonetheless, most of us do use modules, and that automagically installs into the /lib/modules directory tree so there is some splaying.
Aaron Gaudio
"The fool finds ignorance all around him.

when to final 2.2? (1)

Ken Broadfoot (3675) | about 16 years ago | (#2047143)

Geez, download it.. run it.. report the problems.

Stop whining and become part of the 'team'.

Use "patch" to apply patch (1)

roystgnr (4015) | about 16 years ago | (#2047144)

How ironic. The sequence I use (OK, I'm still on 2.1.131, but same principles apply) is:

cd /usr/src
bunzip2 patch-2.1.131.bz2 #or gunzip if applicable
patch -p0 patch-2.1.131

(the -p0 tells it not to strip any directories from the filenames being patched)

Why we use RPMs (1)

jtseng (4054) | about 16 years ago | (#2047145)

IT SAVES TIME!!! Plus I don't want to dink around with tar files and patches to the point of destroying my system. I've already installed 2.0.36-1 in my RH52 system at home and work with a minimum of fuss. IMHO the RPM system is why RH is the leading distro in the US.

IP Forwarding... (1)

eGabriel (5707) | about 16 years ago | (#2047146)

If you are going from a 2.0 to 2.2 kernel, remember that IP Forwarding is off by default, and you need to echo a '1' to the appropriate file in proc (i don't recall it... look at the IP Chains page) to enable it. My masquerading was broken for two weeks until I found this out. Now it works like a champ. Go 2.2!

Why is it nessessary for 2.2.0 to be released soon (1)

xQx (5744) | about 16 years ago | (#2047147)

There are comments on here from people wanting 2.2.0 to be released soon...

I personally would not like to see it released after first quarter this year, but I don't understand why it is so important to people to have 2.2.0 released.

Linux kernel 2.2 is currently in a feature freeze, which means the current pre release does everything the final kernel will do. So why is it so important for 2.2.0 to be released?

Why don't you, the people who want to use 2.2.0 final, just use pre5 AS IF IT WERE FINAL, and only update to the latest pre every 5 releases or when you find a bug in the kernel you are using.

If 2.2.0 were released tomorrow any further bugs that are found would have to be put into a patch, and because end users, not just the `beta testers' will have to apply this, linus will probably want to wait a while before releasing it.

I personally like the releasing of a new pre every 2-3 days, it means I have to compile then re-boot, which makes me feel like I am in windoze again :-) (does flatlining the CPU then having to re-boot for the changes to take effect to install software remind anyone else of a certain OS? *grin*)

hmm... patch? (1)

Spoke (6112) | about 16 years ago | (#2047148)

This assumes that your patch-2.2.0-pre5 is in /usr/src, and you uncompressed linux-2.2.0-pre4 to /usr/src/linux.

cd /usr/src/linux
patch -p1 /usr/src/patch-2.2.0-pre5

And you'll be done!

rpms? (1)

tsikora (6430) | about 16 years ago | (#2047149)

Sorry the Real Linux world is a tar world. Building it youself with tars and *new*
bz2 are the standard. Gimmicks need not apply.

Mirrors slow in mirroring (1)

aXi (6533) | about 16 years ago | (#2047150)

Last night (23:00 gmt+1 time) I found the pre5 patch and complete source on ftp.kernel.org, on a completely free system, there where almost no users at all online. Yet I noticed that none of the mirrors had it. So please, whoever posts kernel kernel info on slashdot, look on the mirrors ( all of them ) if it is allready available there.


when to final 2.2? (1)

eataTREE (7407) | about 16 years ago | (#2047151)

Well, they could pull a Microsloth and release it as-is, even though it still contains bugs. Or they could do what they're doing, make multiple prereleases and correct the bugs in each, then making sure that the bugfixes do not engender new bugs, so when they do release 2.2.0 final, it's stable and works. Which would you prefer? If you want to speed up the release of the final 2.2.0 kernel, install the latest prerelease and submit intelligent bug reports.

Cyrix (1)

Fantome (7951) | about 16 years ago | (#2047152)

Are the Cyrix 6x86 chips still broken? Mine seems to be. I've tried all the patches... compiled it for 386, etc...
I guess it's time for the real stuff.

This must be me, it can't be the kernel... (1)

AraQniD (8255) | about 16 years ago | (#2047153)

> depmod should show ppp.o depending on bsd_comp.o and ppp_deflate.o

no no no no no no no!

bsd_comp and ppp_deflate depend on ppp, not the other way round!

using aliases is the right way. the kernel doesn't know that ppp-compress-24 is bsd_comp, and doesn't need to!

this approach means that a compression module will only be loaded if it is going to be used: if your ppp peer doesn't support compression, the modules won't be loaded, and everyone's happy, yes?

I should imagine that you can't load ppp_deflate without having ppp already loaded (could be wrong, can't check while at work), so having ppp *depend* on ppp_deflate would obviously be broken...

Concise list of fixed stuff (1)

walflour (9009) | about 16 years ago | (#2047154)

where can a good list of what got fixed in each pre release be found?

IP_MASQ_F_DLOOSE: I just reported this... (1)

NatePuri (9870) | about 16 years ago | (#2047155)

I don't do -ac patches because I'm too lazy to undo them before the next one. Pre6 should have this fixed; at least I hope so I'm in the middle of configuring a firewall so this bug wrecks the effort. Patienly waiting...

Is why I use .deb and compile my own (1)

NatePuri (9870) | about 16 years ago | (#2047156)

Redhat is the leading distro because of the easy installation. Debian is the best distro because of .deb, dpkg, and apt. When you learn more you'll move up. I needed RedHat for on month before graduating to debian. When you find you can't upgrade sw you want because of rpms don't let you acquire the necessary dependencies or won't overcome conflicts you'll check out debian, and you'll love it. Aside from that, that rpm kernel you installed has options you don't need. You could reduce the size of the kernel by typing make clean, make menuconfig, make dep, make bzImage (if it's that big) or make zImage, then make bzlilo to install it, make modules, make modules_install, that's it, reboot. Participate in the linux community and report bugs. Trust me, if I can do it, you can too.

when to final 2.2? (1)

i22y (10479) | about 16 years ago | (#2047157)

It's been forever in coming for pre-2.2. when to final?

Almost three times faster compiling! (1)

Syberghost (10557) | about 16 years ago | (#2047158)

You do realize that you can configure that, right?

Nothing beats the Sex Sells Ads on /. (1)

daviddennis (10926) | about 16 years ago | (#2047159)

Hey, it beats MSCE books if nothing else. :-)


No ISDN in 2.2.0 (1)

Neil Rubin (11261) | about 16 years ago | (#2047160)

Well, if a functional patch exists, then ISDN users or their distribution maintainers can apply it themselves. If no functional patch exists, even now, then it probably isn't worth holding up the release of 2.2.0 for it. Annoying, but...

In either case, it is on Alan Cox's todo list, and I'm sure that it will be fixed early in the 2.2.x series.

Mousewheel stopped working (1)

SkurfGod (11388) | about 16 years ago | (#2047161)

Can I use my mousewheel in X? Would someone mind pointing me in the right direction for info on this?

Take your time, Linus! (1)

Stiletto (12066) | about 16 years ago | (#2047162)

pre-5 was the first one to work for me, so obviously they still have a few issues to work out! I'd rather they release 20 "pre" instead of taking the Microsoft route and calling a buggy product final.

nothing is ever finished.. (1)

bishop6 (12147) | about 16 years ago | (#2047163)

once an OS or software is finished to the point of no improvement..we should not use computers anymore.

AC saves your day :) (1)

Ween (13381) | about 16 years ago | (#2047164)

go get
ftp://ftp.linux.org.uk/pub/linux/alan/2.2pre/pat ch-2.2.0pre5-ac1.bz2

and put it in /usr/src/linux

patch then recompile .. its works now :)

talking windows users is where I draw the line ..

or better yet... (1)

dangerboy (95056) | about 16 years ago | (#2047165)

don't bother visiting slashdot anymore.

D.A.R.E. to keep your kids off drugs. (1)

dangerboy (95056) | about 16 years ago | (#2047166)

you smoke too much crack. sure, in a MS world where your forced to use the Man's inflated disfunctional kernel, precompiled updates would be fine. but in a world where you can actually fine tune your computer's abilities, it simply isn't. download the tar and take a bite out of crime.

vga consoles (1)

dangerboy (95056) | about 16 years ago | (#2047167)

is it just me, or are vga consoles annoying? i come from an ascii art background so i might be biased to the oldskewl, but...i'm just wondering.

lilo error message (1)

dangerboy (95056) | about 16 years ago | (#2047168)

i get an error message because lilo doesn't recognize the "video=" option. does anybody know how to correct this? i'm using lilo version 21
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?