Prev: xterm vs. [m]rxvt (WAS: Re: Corporate creep in Linux?(mini-rantette))
Next: hugesmp.s and initrd.img
From: Grant on 23 Sep 2009 07:08
On Wed, 23 Sep 2009 07:12:09 +0000 (UTC), emmel <emmel(a)invalid.invalid> wrote:

>Thus Grant spoke:
>
>> On Tue, 22 Sep 2009 17:54:23 +0000, +Alan Hicks+ <alan(a)lizella.netWORK> wrote:
>>
>> ...
>>>On 2009-09-18, emmel <emmel(a)invalid.invalid> wrote:
>>>>> No, it can't call lilo for you, because some of us use GRUB. Some
>>>>> probably even use other boot managers.
>>>>
>>>> Doesn't stop the kernel make script. And I haven't heard anyone
>>>> complaining about that.
>>>
>>>That's because no one uses that argument in the kernel's Makefile
>>>anymore. I obviously can't speak for everyone, but I know that it's
>>>been sometime since I heard of anyone using make in the kernel's source
>>>directory to re-run lilo. For one, a lot of people don't use lilo
>>>anymore, but for another, most things require initrds these days.
>>
>> I disagree here. The kernel's 'make install' calls out to
>> ~/bin/installkernel or /sbin/installkernel.
>
>It does? Doesn't seem to even exist on my box.

That's right, slackware dosen't provide an installkernel script -- it's
only an optional kernel build feature. The biggies (Suse, etc) use it.
>
>> I choose not to use initrd, can't see the point for custom kernels here.
>
>Well, I need initrd for encrypted root and custom kernels are something
>of a habit for me. Although it was the only way to make my laptop's
>hardware behave before it was as old as it is now.

Oh I'm sure there's good use for initrd. I avoid it for simple systems.

Grant.
--
http://bugsplatter.id.au
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: xterm vs. [m]rxvt (WAS: Re: Corporate creep in Linux?(mini-rantette))
Next: hugesmp.s and initrd.img