....will go down in history as one of the most fucked up kernels
ever released.

We can't even get the damn kernel to install modules upon boot. In
fact, the only way we can load any module is with insmod.

And we are not the only one having this problem. Others here have
posted similar problems and a quick google search shows that all
kinds of people are having problems loading modules.

This is pathetic.

Linux is rapidly approaching the point where it can no longer be
maintained at the kernel level by volunteers (amateurs). It reached
the point long ago where is couldn't be maintained at the user level
by the average user.

Linux is very, very, close to death.

cordially, as always,

rm

On Thu, 15 Feb 2007 00:15:58 +0000, rm wrote:

> ...will go down in history as one of the most fucked up kernels ever
> released.
>
And you thought .19 was any good?

> We can't even get the damn kernel to install modules upon boot. In
> fact, the only way we can load any module is with insmod.
>
>
Why do you write in the first person plural all the time. Are you one half
of siamese twins? You're YOU, ME, I, one person.

> And we are not the only one having this problem. Others here have
> posted similar problems and a quick google search shows that all kinds
> of people are having problems loading modules.
>
I am not surprised. Sometimes pushing out an update for the sake of
pushing out an update is silly.

> This is pathetic.
>
Troublesome.

> Linux is rapidly approaching the point where it can no longer be
> maintained at the kernel level by volunteers (amateurs). It reached the
> point long ago where is couldn't be maintained at the user level by the
> average user.
>
The average user cannot work Linux on a long term basis. An experiment
only. Curiosity piece. However, for a knowledgeable person, technically
savvy, Linus is not only fun, but productive.

> Linux is very, very, close to death.
>
Not really. Look what IBM is doing, starting a whole new division just for
helping clients with Open Source and Linux, in particular. There's money
to be made in services. http://biz.yahoo.com/iw/070212/0214125.html, IBM
Offers Customers Freedom of Choice With New Open Client Solution for
Enterprise PCs


> cordially, as always,
>
> rm

You just love stirring up the pot. BTW, what has this to do with Slackware?

--
Peter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

rm@biteme.org wrote:
> ...will go down in history as one of the most fucked up kernels
> ever released.
>
> We can't even get the damn kernel to install modules upon boot. In
> fact, the only way we can load any module is with insmod.

Then you should go back to using windows.

> And we are not the only one having this problem. Others here have
> posted similar problems and a quick google search shows that all
> kinds of people are having problems loading modules.

I'm having no problem at all:

bradl@bellicha:~> uname -a
Linux bellicha 2.6.20 #1 Mon Feb 5 16:01:13 PST 2007 x86_64 x86_64
x86_64 GNU/Linux
bradl@bellicha:~>

Problem Exists Between Keyboard and Chair.

> This is pathetic.

Closest you'll ever be to flattering yourself.

> Linux is rapidly approaching the point where it can no longer be
> maintained at the kernel level by volunteers (amateurs). It reached
> the point long ago where is couldn't be maintained at the user level
> by the average user.

So you admit you're the average user. You really should take
your own advice. Go back to using windows. Enjoy that $400 you're
wasting for that EULA. I'll just sit here and laugh at you.

> cordially as always,

Valentine's day is the closest you'll ever be to seeing, let
alone being cordial.

BL.
- --
Brad Littlejohn | Email: tyketto@sbcglobal.net
Unix Systems Administrator, | tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF075tyBkZmuMZ8L8RAj5LAJ9z+hQboLe0JNErsTmwjv oiLsTucwCfYiUC
Nt4dTDiPBNDg0OFzfZjpn6k=
=EHgG
-----END PGP SIGNATURE-----

A Guy Called Tyketto <tyketto@sbcglobal.net.invalid> wrote:

[pgp trash troll delete]

Hi, there, tiny dick.

> rm@biteme.org wrote:
>> ...will go down in history as one of the most fucked up kernels
>> ever released.
>>
>> We can't even get the damn kernel to install modules upon boot. In
>> fact, the only way we can load any module is with insmod.
>
> Then you should go back to using windows.

We do go back to windoze when the occasion demands it. Don't you?

>> And we are not the only one having this problem. Others here have
>> posted similar problems and a quick google search shows that all
>> kinds of people are having problems loading modules.
>
> I'm having no problem at all:

We have no problem at all, neither, until we start to fuck around
with modules. The problem probably has something to do with the
fact that we haven't used modules in years. And the "new" module
software seems to require that old module software be installed,
beforehand.

That's just about the dumbest thing we have ever seen.

You probably don't use any modules. In fact, you probably don't
even know what a module is.

What weight are you up to on your penis extender?

cordially, as always,

rm

On Thu, 15 Feb 2007 00:15:58 GMT
rm@biteme.org wrote:

> ...will go down in history as one of the most fucked up
> kernels ever released.
>
> We can't even get the damn kernel to install modules upon
> boot. In fact, the only way we can load any module is with
> insmod.

I posted my troubles with 2.6.20 modules before. A straight
..config from 2.6.18.5 would not migrate correctly with the
2.6.20 sources 'make oldconfig' or 'make menuconfig'. At least
the kernel/modules built with it were lame-brain, in my case ...

After some days of experimenting and upgrading
module-init-tools to the latest, I did get it to load modules.
I posted the 2.6.20 config that worked for me, below.

My slackware build is for an embedded slackware clone, but it
will probably be a good start for any one trying to migrate to a
new Slackware 2.6.20 Linux build.

ftp://ftp.sysdev.org/pub/lintools/EB...0-FB-60MB-i486

TonyB

There are 10 types of people in this world, those that read
binary and those who don't!

--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers

A Guy Called Tyketto <tyketto@sbcglobal.net.invalid> wrote:
>
> rm@biteme.org wrote:
>>
>> We can't even get the damn kernel to install modules upon boot. In
>> fact, the only way we can load any module is with insmod.
>
> Then you should go back to using windows.

An example of a "kernel" that long ago reached the point at which it could
no longer be maintained by professional software developers.

- Kurt

On Thu, 15 Feb 2007 00:15:58 +0000, rm wrote:

> ...will go down in history as one of the most fucked up kernels
> ever released.

LOL. Works fine here, n00b.

> We can't even get the damn kernel to install modules upon boot. In
> fact, the only way we can load any module is with insmod.

That's because you're a clueless n00b, and a moron.

> And we are not the only one having this problem. Others here have
> posted similar problems and a quick google search shows that all
> kinds of people are having problems loading modules.

Yep, "all kinds" of morons.

> This is pathetic.

Yes, you are.

> Linux is rapidly approaching the point where it can no longer be
> maintained at the kernel level by volunteers (amateurs). It reached
> the point long ago where is couldn't be maintained at the user level
> by the average user.

So you are below-average. Everyone here already knew that.

> Linux is very, very, close to death.

Har! Idiot.

> cordially, as always,

Smeg off, dingus.

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

Peter wrote:
> On Thu, 15 Feb 2007 00:15:58 +0000, rm wrote:
>
>> ...will go down in history as one of the most fucked up kernels
>> ever released.
>
> And you thought .19 was any good?
>
>> We can't even get the damn kernel to install modules upon boot.
>> In fact, the only way we can load any module is with insmod.
>
> Why do you write in the first person plural all the time. Are you
> one half of siamese twins? You're YOU, ME, I, one person.

rm is a known troll. Please do not feed it.

--
<http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfocus.com/columnists/423>

"A man who is right every time is not likely to do very much."
-- Francis Crick, co-discover of DNA
"There is nothing more amazing than stupidity in action."
-- Thomas Matthews

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

rm@biteme.org wrote:
> A Guy Called Tyketto <tyketto@sbcglobal.net.invalid> wrote:
>
> [pgp trash troll delete]
>
> Hi, there, tiny dick.

You still love me.

>> rm@biteme.org wrote:
>>> ...will go down in history as one of the most fucked up kernels
>>> ever released.
>>>
>>> We can't even get the damn kernel to install modules upon boot. In
>>> fact, the only way we can load any module is with insmod.
>>
>> Then you should go back to using windows.
>
> We do go back to windoze when the occasion demands it. Don't you?

Nope. Never had to, never need to.

>>> And we are not the only one having this problem. Others here have
>>> posted similar problems and a quick google search shows that all
>>> kinds of people are having problems loading modules.
>>
>> I'm having no problem at all:
>
> We have no problem at all, neither, until we start to fuck around
> with modules. The problem probably has something to do with the
> fact that we haven't used modules in years. And the "new" module
> software seems to require that old module software be installed,
> beforehand.

You've contradicted yourself here, Roger. You say you've had
problems beyond problems, and this is the worst kernel. now you say you
don't have any problems. You definitely have problems, all right.

> That's just about the dumbest thing we have ever seen.
>
> You probably don't use any modules. In fact, you probably don't
> even know what a module is.

I know I shouldn't, but here, troll. sit and eat your food like
the dog you are:

bradl@bellicha:~> cat /etc/slackware-version
Slackware 11.0.0 (x86_64)
bradl@bellicha:~> uname -snrvm
Linux bellicha 2.6.20 #1 Mon Feb 5 16:01:13 PST 2007 x86_64
bradl@bellicha:~> lsmod
Module Size Used by
softdog 7132 2
ipt_LOG 6912 2
xt_limit 3712 4
xt_tcpudp 4096 38
xt_state 3136 3
nf_nat_ftp 4160 0
nf_conntrack_ftp 10976 1 nf_nat_ftp
iptable_filter 3712 1
iptable_nat 7812 0
ip_tables 20192 2 iptable_filter,iptable_nat
nf_nat 20076 2 nf_nat_ftp,iptable_nat
nf_conntrack_ipv4 18704 5 iptable_nat
nf_conntrack 63400 6 xt_state,nf_nat_ftp,nf_conntrack_ftp,iptable_nat,n f_nat,nf_conntrack_ipv4
x_tables 21192 6 ipt_LOG,xt_limit,xt_tcpudp,xt_state,iptable_nat,ip _tables
reiserfs 207472 5
snd_fm801 22560 0
snd_tea575x_tuner 4736 1 snd_fm801
snd_intel8x0 36520 0
videodev 28224 1 snd_tea575x_tuner
v4l2_common 26496 1 videodev
v4l1_compat 12932 1 videodev
snd_ac97_codec 109528 2 snd_fm801,snd_intel8x0
snd_opl3_lib 11328 1 snd_fm801
snd_hwdep 11016 1 snd_opl3_lib
snd_mpu401_uart 9024 1 snd_fm801
ide_cd 41440 0
cdrom 36840 1 ide_cd
k8temp 6656 0
ac97_bus 3136 1 snd_ac97_codec
hwmon 3872 1 k8temp
snd_pcm 78412 3 snd_fm801,snd_intel8x0,snd_ac97_codec
snd_rawmidi 26816 1 snd_mpu401_uart
snd_timer 23944 2 snd_opl3_lib,snd_pcm
snd_seq_device 9172 2 snd_opl3_lib,snd_rawmidi
ohci_hcd 20484 0
i2c_nforce2 6528 0
snd 63080 10 snd_fm801,snd_intel8x0,snd_ac97_codec,snd_opl3_lib ,snd_hwdep,snd_mpu401_uart,snd_pcm,snd_rawmidi,snd _timer,snd_seq_device
evdev 11584 0
forcedeth 42244 0
ehci_hcd 30412 0
usbcore 137808 3 ohci_hcd,ehci_hcd
e100 36752 0
snd_page_alloc 10960 2 snd_intel8x0,snd_pcm
mii 6592 1 e100
8250_pnp 12288 0
soundcore 9056 1 snd
8250 25416 1 8250_pnp
fm801_gp 4864 0
serial_core 21952 1 8250
parport_pc 36904 0
gameport 17040 2 fm801_gp
parport 40460 1 parport_pc

And those are just the ones LOADED. Like I said. Walk on home,
boy. Your daddy Billy Goat Gates is calling, and wants to squeeze your
head.

BL.
- --
Brad Littlejohn | Email: tyketto@sbcglobal.net
Unix Systems Administrator, | tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF1B4RyBkZmuMZ8L8RAkLYAJ9wLoSFFGWqLmv9Ze7/JVKSzqtOcACfcTdJ
HglSXApODUKyksN9xHIIerw=
=ilNw
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hufnus <tonyb@sysdev.org> wrote:
>
> I posted my troubles with 2.6.20 modules before. A straight
> .config from 2.6.18.5 would not migrate correctly with the
> 2.6.20 sources 'make oldconfig' or 'make menuconfig'. At least
> the kernel/modules built with it were lame-brain, in my case ...
>
> After some days of experimenting and upgrading
> module-init-tools to the latest, I did get it to load modules.
> I posted the 2.6.20 config that worked for me, below.

That should be the major thing you'd have to upgrade. My
..config migrated cleanly from 2.6.17.14 and 2.6.16.39. As long as you
have the latest module-init-tools, and, if you are running it, udev, you
should be plenty fine.

BL.
- --
Brad Littlejohn | Email: tyketto@sbcglobal.net
Unix Systems Administrator, | tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF1B7EyBkZmuMZ8L8RAlCuAJ4uY8o73xkRtJkN+tpBWK BQmW8I+QCguxbc
DURga0Jxk4V3as/EAsfcSTI=
=FbbS
-----END PGP SIGNATURE-----