13 Aug
2004
13 Aug
'04
6:03 p.m.
Something that helps to is to never remove your known working kernel
entry from your bootloader, and make your new kernel the secondary
manually selected kernel on your first boot. This way if your kernel is
hosed for some reason, you should always be able to recover your system
with minimal pain by rebooting into your default working kernel.
later,
Steve
Andrew Dahlin wrote:
honestly, compiling a kernel is trivial once you build
one successfully.
the first time will take a few hours to get it right (tops), but
by the time
you're done, you know exactly what you're doing. i can configure a kernel
from scratch in about 20 minutes... and i'm not a hacker or anything... i
just know what i need. i'm not saying everyone should build their own
kernel, but if you install your distro's sources (with their .config), it's
fairly risk free. just back up your old kernel. [OT: if you run lilo, don't
forget to run lilo after copying over the new kernel. TONS of people don't
realize this their first time]
--Andrew
On Thu, 12 Aug 2004 21:35:36 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
>On Thu, 2004-08-12 at 21:25, Russell Hanaghan wrote:
>
>
>>I appreciate both points guys...
>>
>>I think the main one to take from this is a classic;
>>"If it ain't broke, Don't fix it!" :)
>>
>>I find myself digging into a perfectly tight operating system with all
>>the array of perfectly functional audio apps I use....and hours and
>>hours later sit there pissed off and frustrated because I didn't achieve
>>any noteworthy results from it all...and I only like to do so much
>>_learning_ at a time! :)
>>
>
>One other tip I found useful is, if you do have to compile your own
>kernel from a kernel.org kernel, use the .config from your vendor's
>kernel source package. That way you get a kernel that is close as
>possible to the vendor kernel, and you minimize the chance of breaking
>anything that currently works.
>
>Lee
>
13 Aug
13 Aug
6:26 p.m.
New subject: [linux-audio-user] what window manager are you using?
On Fri, 2004-08-13 at 15:48, Stephen Hassard wrote:
Something that helps to is to never remove your known
working kernel
entry from your bootloader, and make your new kernel the secondary
manually selected kernel on your first boot. This way if your kernel is
hosed for some reason, you should always be able to recover your system
with minimal pain by rebooting into your default working kernel.
later,
Steve
Andrew Dahlin wrote:
99% of the time, if you compile a new kernel and it won't boot, it's
because you forgot to enable some driver that's required to boot your
machine. So, using the vendor's .config is a pretty good way to ensure
that if your old kernel worked, the new one will.
Actually, now there's an even better way. I think this feature is only
available on 2.6 kernels. The .config used to compile the running
kernel is available in /proc/config.gz, so you can do:
zcat /proc/config.gz > .config
and be pretty much guaranteed to get the exact same working config that
you have running.
Of course it's still a good idea to keep the old kernel accessible. But
you can reduce your failure rate to almost zero.
Lee
honestly, compiling a kernel is trivial once you
build one successfully.
the first time will take a few hours to get it right
(tops), but by the time
you're done, you know exactly what you're doing. i can configure a kernel
from scratch in about 20 minutes... and i'm not a hacker or anything... i
just know what i need. i'm not saying everyone should build their own
kernel, but if you install your distro's sources (with their .config), it's
fairly risk free. just back up your old kernel. [OT: if you run lilo, don't
forget to run lilo after copying over the new kernel. TONS of people don't
realize this their first time]
> 
7:12 p.m.
New subject: [linux-audio-user] what window manager are you using?
On Fri, Aug 13, 2004 at 04:11:49PM -0400, Lee Revell wrote:
Actually, now there's an even better way. I think
this feature is only
available on 2.6 kernels. The .config used to compile the running
kernel is available in /proc/config.gz, so you can do:
zcat /proc/config.gz > .config
... but I think the ablity to embed the .config info in the kernel is
itself a feature that you can enable or disable in the config menu, so
don't cut yourself off by forgetting to enable it :-)
Of course it's still a good idea to keep the old
kernel accessible.
That's the golden rule. You only have to fail once to appreciate the
significance. You can recover with a bootable rescue CD but
it's much harder work. (been there, etc.)
--
Anahata
anahata(a)treewind.co.uk -+- http://www.treewind.co.uk
Home: 01638 720444 Mob: 07976 263827
7589
days inactive
7589
days old
linux-audio-user@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
anahata -
Lee Revell -
Stephen Hassard