Peter Jay Salzman said:
(Very good information from Pete cut from here)
> also, like ME, i keep many copies of the kernel, with labels:
>
> bleedinglinux
> newlinux
> linux
> oldlinux
> mustylinux
> crustylinux
>
> so i only keep 6 of them. if i could think of two more cute names,
> maybe i'd keep
hi chris,
aside from ME's suggestion of /boot/kernel, i also have /boot/configs
where all my .config files go (name 2.6.1-1, 2.6.1-2, etc) and
/boot/tarballs where all my kernel sources and patches go. Like ME, the
first thing I do with a new system is have lilo point to the actual
image rather t
Gah! That would have been tough to diagnose here. :-)
Ons of the things I do after I install a system is to make a directory
like /boot/kernels
and copy my kernels there, including the one which came with the system
install.
All kernels go there, including new ones.
Symlinks are deleted and lio
Dear Peter and List Members,
I'm sorry for posting too much unnecessary information - especially
since the problem had nothing to do with .config anyway! In my
frustration, I tried reinstalling the custom 2.6.3 kernel that had booted
previously, and it would no longer boot (same error as 2.6.
On Fri, 28 May 2004, ME wrote:
[...]
> Some hardware also requires supprot for bug fixes on certain kinds of
> interfaces also be part of the kernel as static selections. (Seek the IDE
> interface support section, and note the various IDE/ATA interface chipset
> bug fixes and work arounds... if y
Chris Jenks said:
> On Fri, 28 May 2004, Ken Bloom wrote:
>
>> The most common cause of this problem is when your root filesystem
>> isn't compiled into the kernel and you aren't using an initrd.
>
> Dear Ken,
>
> It's true that I have avoided using an initrd. Do I have to use it to go
> from k
On Fri, 28 May 2004, Ken Bloom wrote:
> The most common cause of this problem is when your root filesystem
> isn't compiled into the kernel and you aren't using an initrd.
Dear Ken,
It's true that I have avoided using an initrd. Do I have to use it to go
from kernel 2.6.3 to 2.6.5? Does co
On Fri, May 28, 2004 at 03:45:01PM -0700, Chris Jenks wrote:
>
> I wrote recently about a problem I was having getting PCMCIA working
> under a custom 2.6.5 kernel. Actually, I meant the 2.6.3 kernel, because
> when I tried upgrading to the 2.6.5 kernel source that recently appeared
> in the Sar
I wrote recently about a problem I was having getting PCMCIA working
under a custom 2.6.5 kernel. Actually, I meant the 2.6.3 kernel, because
when I tried upgrading to the 2.6.5 kernel source that recently appeared
in the Sarge source tree, the boot fails after about one page of messages.
The fo
