On Tue, Mar 06, 2007 at 04:48:19AM -0600, Hugo Vanwoerkom wrote:
Chris Bannister wrote:
On Sun, Mar 04, 2007 at 02:19:54PM -0600, Hugo Vanwoerkom wrote:
[..]
But how does he know that initrd.img-2.6.18-4-486 is the 'newest kernel'
as the man-page has it?
-uThis mode updates an existing
On Sun, Mar 04, 2007 at 02:19:54PM -0600, Hugo Vanwoerkom wrote:
Hi,
I run this:
~Sun Mar 04-13:57:19SDA6# update-initramfs -u
and I get:
/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
That happens to be true. (Surprise!)
But how does he know that
Chris Bannister wrote:
On Sun, Mar 04, 2007 at 02:19:54PM -0600, Hugo Vanwoerkom wrote:
Hi,
I run this:
~Sun Mar 04-13:57:19SDA6# update-initramfs -u
and I get:
/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
That happens to be true. (Surprise!)
But how does he know that
Hi,
I run this:
~Sun Mar 04-13:57:19SDA6# update-initramfs -u
and I get:
/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
That happens to be true. (Surprise!)
But how does he know that initrd.img-2.6.18-4-486 is the 'newest kernel'
as the man-page has it?
uname -r has:
Hugo Vanwoerkom wrote:
Hi,
I run this:
~Sun Mar 04-13:57:19SDA6# update-initramfs -u
and I get:
/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
That happens to be true. (Surprise!)
But how does he know that initrd.img-2.6.18-4-486 is the 'newest kernel'
as the man-page has
On Sun, Mar 04, 2007 at 04:29:24PM -0600, Hugo Vanwoerkom wrote:
Hugo Vanwoerkom wrote:
Hi,
I run this:
~Sun Mar 04-13:57:19SDA6# update-initramfs -u
and I get:
/boot/initrd.img-2.6.18-4-486 does not exist. Cannot update.
That happens to be true. (Surprise!)
But how does he
6 matches
Mail list logo
