I located a "how to" on configuring and installing a new Linux Kernel on
openSUSE 10.3
http://en.opensuse.org/Configure,_Bu...m_Linux_Kernel

To put it mildly, the procedure appears to be daunting, and I am hesitant to
begin it without some reassurances from those who have tried it.

Are there any "Kernel Experts" who wish to come forth with words of
encouragement or discouragement?

Thanks,

Godzilla

Godzilla wrote:
> I located a "how to" on configuring and installing a new Linux Kernel on
> openSUSE 10.3
> http://en.opensuse.org/Configure,_Bu...m_Linux_Kernel
>
> To put it mildly, the procedure appears to be daunting, and I am hesitant to
> begin it without some reassurances from those who have tried it.
>
> Are there any "Kernel Experts" who wish to come forth with words of
> encouragement or discouragement?

I never run the stock kernel; always running on a custom build.

http://groups.google.com/group/alt.o...a3e4db7abedf7d

Godzilla wrote:
> I located a "how to" on configuring and installing a new Linux Kernel on
> openSUSE 10.3
> http://en.opensuse.org/Configure,_Bu...m_Linux_Kernel
>
> To put it mildly, the procedure appears to be daunting, and I am hesitant to
> begin it without some reassurances from those who have tried it.
>
> Are there any "Kernel Experts" who wish to come forth with words of
> encouragement or discouragement?

Unlike other distributions, your kernel's current configuration
is actually STORED as part of the kernel, zcat /proc/config.gz

You can do, make cloneconfig
before you try bringing up the graphical or non-graphical
kernel configuration tools in order to make sure you at
least have the options that your current kernel has set... then
you can modify from there.

The instructions at the link above are not that bad.. and it
REALLY isn't all that daunting. I think after you go
through it, you'll find it isn't so bad. What is "bad" is the
number of tweakable things. It's immense nowadays. But
have fun.... I don't know what everything means in the
kernel config, I imagine that very few do.

Also, there isn't anything preventing you from having and trying
out multiple kernels.... just use different grub lines in
your /boot/grub/menu.lst. This way you can always get back
to your "good" running kernel in case you create a bad one.

So... I will encourage you to play with building your own
kernel. There are ups and downs. I've certainly built some
that weren't so great... big deal... just make another one!

One of the nice things about Linux.

Godzilla wrote:

> I located a "how to" on configuring and installing a new Linux Kernel on
> openSUSE 10.3
> http://en.opensuse.org/Configure,_Bu...m_Linux_Kernel
>
> To put it mildly, the procedure appears to be daunting, and I am hesitant
> to begin it without some reassurances from those who have tried it.
>
> Are there any "Kernel Experts" who wish to come forth with words of
> encouragement or discouragement?
>
> Thanks,
>
> Godzilla
For normal suse distributions there is not much to win with compiling a new
kernel. Most options are modules which you can build separately. I used
once a suse kernel to get some first experiences with RTAI (realtime
kernels) on an old PC. If you want to really dig into kernel stuff I
strongly recommend to buy a linux based microprocessor board and run/build
a vanilla kernel on it. Also check out the LFS website (Linux from scratch)
taco

taco wrote:
> For normal suse distributions there is not much to win with compiling a new
> kernel.

He has a specific need: TrueCrypt.

> Most options are modules which you can build separately.

No idea wether that is an option or not.

houghi
--
You are about to enter another dimension, a dimension not only of
sight and sound but of mind. A journey into a wondrous land of
imagination. Next stop, Usenet!

houghi wrote:

> taco wrote:
>> For normal suse distributions there is not much to win with compiling a
>> new kernel.
>
> He has a specific need: TrueCrypt.
>
>> Most options are modules which you can build separately.
>
> No idea wether that is an option or not.
>
> houghi

Thanks for reminding others of why I was interested in compiling the kernel.
After reading a few posts and the extensive discussion link about compiling
from two knowledgeable colleagues with differing outlooks, I remain on the
fence about my own desires and abilities. In a much earlier post, I
described how much I admired TrueCrypt and then how it failed me when the
kernel of openSUSE changed. This leads me to wonder if the future of
TrueCrypt will remain at least partially kernel dependent.

Godzilla

Godzilla schreef:
> houghi wrote:
>
>> taco wrote:
>>> For normal suse distributions there is not much to win with compiling a
>>> new kernel.
>> He has a specific need: TrueCrypt.
>>
>>> Most options are modules which you can build separately.
>> No idea wether that is an option or not.
>>
>> houghi
>
> Thanks for reminding others of why I was interested in compiling the kernel.
> After reading a few posts and the extensive discussion link about compiling
> from two knowledgeable colleagues with differing outlooks, I remain on the
> fence about my own desires and abilities. In a much earlier post, I
> described how much I admired TrueCrypt and then how it failed me when the
> kernel of openSUSE changed. This leads me to wonder if the future of
> TrueCrypt will remain at least partially kernel dependent.
>
> Godzilla

I'm not reading this group everyday, so maybe I missed your earlier
posts, but why TrueCrypt while yast also provide disk encryption.

Canned wrote:
> I'm not reading this group everyday, so maybe I missed your earlier
> posts, but why TrueCrypt while yast also provide disk encryption.

TrueCrypt does much more then just disk encryption. Just look at the
TrueCrypt site to what it can do for details, but some important
differences are:
1) It can be used on a user level. This means that multiple people can
use it at the same time if you have a multi-user enviroment. So
encryption is with the user, not the system admin.

2) It has hidden parts. This means if you are forced to hand over your
password, you can and you just give them one. Another password can be
used to access the hidden parts,

The multi user part can be usefull in any enviroment where you desire to
respect peoples privacy.

The hidden part canbe usefull if you plan on going to the USofA. When
they demand your password, you give it and they see your 'boobies
pictures'. This can be an excuse to have them hidden.

Now with the real password, you can reveal your hidden information
within the hidden information on how to liberate the USofA from the
situation it is in and bring democracy to the country.

So while one is on a system level, the other is on a user level.

houghi
--
You are about to enter another dimension, a dimension not only of
sight and sound but of mind. A journey into a wondrous land of
imagination. Next stop, Usenet!