Re: Kernel recompile has left /boot empty
From: Matt Bostock (matt_at_mattbostock.com)
Date: 03/15/04
- Next message: Matt Bostock: "Re: Kernel recompile has left /boot empty"
- Previous message: Richard Steiner: "Re: Which version is best"
- In reply to: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Next in thread: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Reply: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 15 Mar 2004 02:36:17 -0000
It's all ext3, same as the main partition.
When I run:
# du boot -h
It comes up with:
8.0K boot
So it really appears as though there's only the kernel.h left.
Matt
-- Banging your head against a wall uses 150 calories an hour. "Brian Reiahle" <reply@the.newsgroup> wrote in message news:3w85c.91$th6.2039@nnrp1.ozemail.com.au... > Matt Bostock wrote: > > Hi, > > > > I successfully recompiled my kernel (2.4.25), patched with GRSecurity. I'm > > using RedHat9 and Grub bootloader. I tested out the new kernel so that it > > would only load as default once, and then if anything went wrong I could > > simply reboot. Everything went fine, except that I noticed /boot was empty > > apart from containing kernel.h. > > > > I presumed it was normal for 'kernel testing', so I rebooted, made the new > > recompiled kerned the default, and rebooted again. Everything has been > > working fine, expect /boot is still empty except for kernel.h. > > > > I need to recompile the kernel again with some new options, but can't > > because /boot is almost empty. Any idea why it's (almost) empty? > > > > Thanks, > > Matt :) > > Do you have /boot on a seporate partition? > if so, dose it use a different filesystem? > > The first thing that came to mind was that maby the boot scripts faild > to mount /boot ... maby you forgot to add support for it's filesystem? > ... maby a needed module is on a filesystem not mounted until after > /boot failed. > > not sure about the kernel.h though, im just thinking out loud at the moment. It's all ext3, same as the main partition. When I run: # du boot -h It comes up with: 8.0K boot So it really appears as though there's only the kernel.h left. Matt -- Banging your head against a wall uses 150 calories an hour. "Brian Reiahle" <reply@the.newsgroup> wrote in message news:3w85c.91$th6.2039@nnrp1.ozemail.com.au... > Matt Bostock wrote: > > Hi, > > > > I successfully recompiled my kernel (2.4.25), patched with GRSecurity. I'm > > using RedHat9 and Grub bootloader. I tested out the new kernel so that it > > would only load as default once, and then if anything went wrong I could > > simply reboot. Everything went fine, except that I noticed /boot was empty > > apart from containing kernel.h. > > > > I presumed it was normal for 'kernel testing', so I rebooted, made the new > > recompiled kerned the default, and rebooted again. Everything has been > > working fine, expect /boot is still empty except for kernel.h. > > > > I need to recompile the kernel again with some new options, but can't > > because /boot is almost empty. Any idea why it's (almost) empty? > > > > Thanks, > > Matt :) > > Do you have /boot on a seporate partition? > if so, dose it use a different filesystem? > > The first thing that came to mind was that maby the boot scripts faild > to mount /boot ... maby you forgot to add support for it's filesystem? > ... maby a needed module is on a filesystem not mounted until after > /boot failed. > > not sure about the kernel.h though, im just thinking out loud at the moment.
- Next message: Matt Bostock: "Re: Kernel recompile has left /boot empty"
- Previous message: Richard Steiner: "Re: Which version is best"
- In reply to: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Next in thread: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Reply: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|