Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Compiling 2.6.9-1.724 kernel update



On Tue, Jan 18, 2005 at 10:19:37PM -0500, jbk wrote:
> jbk wrote:
> > 
> > >I get a kernel panic when I boot the latest
> > >compile from grub. I can still boot to the

Please be polite and trim quotes in your posts.  :)

> Well the answer is su -. For what ever reason, the
> initrid that is made without it does not have the
> correct information. 

My guess is that it's because of the setting of the $HOME variable.
If you use the -, $HOME gets reset to /root (or whatever root's home
dir is).  If you don't use '-', $HOME remains set to the home dir of
the user who ran su.  Why this might matter is unclear, but is
probably due to a programming error (or, my guess is wrong).

> So the question is, what does initrid make if the file systems are
> compiled into the kernel? There are no modules so what is the other
> crucial information that is stored in the image that boots the
> system?

In fact it makes a file system which the kernel uses during the boot
process.  It contains modules, for sure; but it also contains a file
called linuxrc which controls part of the boot process.  My guess is
that this file is wrong, or just plain missing.

You can look and see what's in the initrd by first gunzipping it to
some convenient file (if it's a gzipped file system image, which is
normally the case).  Then you can do something like the following to
look at the contents:

  # mount -o loop <my_unzipped_initrd> /mnt/tmp

Of course /mnt/tmp must exist.

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail.  Sorry for the inconvenience.  Thank the spammers.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20050118/7e583c3e/attachment.sig>



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org