[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikrynvdOP7qtiHqgmEzuAFTjB=rcN90cBv-VuVG@mail.gmail.com>
Date: Fri, 7 Jan 2011 14:25:16 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Alejandro Riveira Fernández <ariveira@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [GIT] Networking
2011/1/7 Alejandro Riveira Fernández <ariveira@...il.com>:
>> [ Apart from the annoyance of also having to manually copying the
>> firmware files: why the heck doesn't that firmware tree even have a
>> "make firmware-install" makefile or something? The kernel has a "make
>> firmware-install" thing, why doesn't the firmware tree itself have
>> that? Gaah, this is almost as idiotic as trying to install a
>> self-built kernel under Ubuntu ]
>
> Maybe i am just making myself a fool but i'll bite:
> this has allways worked for me
>
> make && sudo make install && sudo make modules_install
> sudo mkintramfs -o /boot/initrd-$kernel_version $kernel_version
> sudo update-grub
Whee. That's not what any of the docs say. And while it is simpler
than what is apparently the "official" method (which involves packages
etc) why doesn't just
make modules_install ; make install
work? That's all I need to do on systems that are friendlier to kernel
developers.
The kernel install scripts run "/sbin/installkernel" exactly so that a
distribution can just make it all work for them. But at least when I
tried it last, it didn't.
Some people claim Ubuntu has no kernel developers. Sometimes I do wonder..
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists