Kernel 2.5.22
DaveAtFraud writes "The latest experimental Linux kernel (2.5.22) is out. The somewhat massive changelog has the details. The patch file is here and the full source is here. If possible use a mirror. I never got 2.5.21 to get beyond single user mode on my dualie so hopefully 2.5.22 will fix that."
I downloaded the Debian 2.2 stable ISO a couple days ago and am looking forward to my second foray into Linux. The first was a short-lived adventure with SuSE which was not unpleasant, but KDE's state at the time left much to be desired.
/.
;-)
I do not run servers as I have neither the need nor the extra money for them, so any Linux device I set up will strictly be a desktop machine. I'll keep everyone up to date with periodic postings here on
I'm sure you all can't wait.
I have been pwned because my
The ChangeLog entry:
kbuild: Pass to fixdep
cpp -MD guesses the target name from the source file name, but not
always correctly, e.g. when compiling fixdep, it generates prequisites
for fixdep.o instead of fixdep.
fixdep now fixes up the -MD generated output to contain the right target,
which is the one we pass on the command line.
This can be fixed another way bu using the option -MQ or MT:
`-MT TARGET'
Change the target of the rule emitted by dependency generation. By
default CPP takes the name of the main input file, including any
path, deletes any file suffix such as `.c', and appends the
platform's usual object suffix. The result is the target.
An `-MT' option will set the target to be exactly the string you
specify. If you want multiple targets, you can specify them as a
single argument to `-MT', or use multiple `-MT' options.
For example, `-MT '$(objpfx)foo.o'' might give
$(objpfx)foo.o: foo.c
`-MQ TARGET'
Same as `-MT', but it quotes any characters which are special to
Make. `-MQ '$(objpfx)foo.o'' gives
$$(objpfx)foo.o: foo.c
The default target is automatically quoted, as if it were given
with `-MQ'.
I'm sure most of our viewers would rather see notices about release of the stable branches (2.2 and 2.4), instead of notices regarding the unstable branch. How about a poll?
are you some kind of moron, or just a flatulent nerd? (no offense to any moderator that might be reading)
return 0;
}
"break some windows"
No need to strain yourself; the factory pre-breaks them for you now.
- Jester
looks like using bitkeeper is really making life easier!
hmm... I thought people learn not to respond to TROLLS
people in here don't get jokes anyway
return 0;
}
You're a fucking retard. No, I haven't seen your baseball.
"Anonymous Coward"
return 0;
}
LINUX is not the problem here.
Filesystem-level encryption, secure IM programs, and p2p programs ARE the problem. All of these are availible on any OS poison you choose (including your precious windows box, which actually has better options in ALL of those fields, except for the open source server).
return 0;
}
it's okay... you can dare to be stupid!
Take some wooden nickels
Look for Mr. Goodbar...
dammit man, you'll have this stuck in my head all day!
finally! another TRUE parody fan in here!
return 0;
}
Hey again, getter_85. If you're not interested in HOT PENGUIN SEX we can always go FUCK SOME GOATS OR SOMETHING. You like goats, right? How about little kids? Alan Cox has the Olsen Twins locked up in his closet...
-- Linus Torvalds
some minor development Linux-kernel release for uberhackers is released, and it receives mention on Slashdot. A major release of FreeBSD goes up, and Slashdot treats it like it's unimportant. I've never even used BSD before and I'm peaved.
oh god, now I have two people stalking me!
return 0;
}
Hopefully I won't go blind replying to my own posting but current is now 2.5.24. It compiles and seems to be stable on my dualie AMD box. Is it my imagination or are the odd development kernels a little more "developmental" than the even ones? So far 2.5.20, 2.5.22 and 2.5.24 have all built with little or no pain while 2.5.21 and 2.5.23 were DOA.
They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.
Ben