public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Deleted my kernel .config
Date: Fri, 23 Jan 2009 02:45:23 -0600	[thread overview]
Message-ID: <497983A3.4090209@gmail.com> (raw)
In-Reply-To: <1232698595.2632.13.camel@mymachine>

Dirk Heinrichs wrote:
> Am Freitag, den 23.01.2009, 01:53 -0600 schrieb ext Dale:
>
>   
>> I'll show this just in case it will give someone ides.
>>     
>
> Here's another approach:
>
> % ll /boot
> insgesamt 9644
> lrwxrwxrwx 1 root root       1 17. Jan 2006  boot -> ./
> drwxr-xr-x 2 root root    1024 21. Mai 2008  grub/
> drwx------ 2 root root   12288 11. Okt 2005  lost+found/
> -rw-r--r-- 1 root root 4892720 22. Jan 14:25 vmlinux-2.6.28.1.gz
> -rw-r--r-- 1 root root 4892272 16. Jan 15:32 vmlinux-2.6.28.gz
> lrwxrwxrwx 1 root root      19 22. Jan 14:26 vmlinux.gz ->
> vmlinux-2.6.28.1.gz
> lrwxrwxrwx 1 root root      17 22. Jan 14:26 vmlinux.old.gz ->
> vmlinux-2.6.28.gz
>
> No System.map (what's it good for, anyway?)
> No .config (it's in /proc/config.gz).
> No need to edit grub.conf as the symlinks are updated using a small
> script (which also removes old module directories from /lib/modules).
> No initrd as an embedded initramfs is used (hence the size of the
> kernels).
>
> Bye...
>
> 	Dirk
>   

But if a kernel gets corrupted or accidentally deleted, there will be no
/proc/config.gz since the kernel won't boot.  I have that turned on here
to but I'm not going to put all my eggs in that one basket.  I couldn't
write a script anyway plus I only update kernels once in a blue moon
anyway.  I'm still running 2.6.23 right now.  The new one is compiled
and ready but I just haven't rebooted in a while.

I was wondering about that system.map thing.  It's been there a long
while.  I just redone my install and I only saved /boot, make.conf,
world and a couple other files, plus my /home naturally.

Dale

:-)  :-)



  reply	other threads:[~2009-01-23  8:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23  2:12 [gentoo-user] Deleted my kernel .config Grant
2009-01-23  2:22 ` Saphirus Sage
2009-01-23  7:37   ` KH
2009-01-23  2:28 ` Crob
2009-01-23  3:03   ` Grant
2009-01-23  8:28     ` Justin
2009-01-23  8:40       ` Dirk Heinrichs
2009-01-23  8:45         ` Justin
2009-01-23  8:57           ` Dirk Heinrichs
2009-01-23  9:47             ` Justin
2009-01-23 13:14           ` Norberto Bensa
2009-01-23 13:19             ` Alejandro
2009-01-23 13:24               ` Justin
2009-01-23 13:51                 ` Dirk Heinrichs
2009-01-23 14:00                 ` Norberto Bensa
2009-01-23 13:44               ` Norberto Bensa
2009-01-23 13:52                 ` Alejandro
2009-01-23 15:09                 ` Dale
2009-01-23 13:24       ` Ricardo Saffi Marques
2009-01-23 14:39       ` Grant
2009-01-23 13:23     ` Ricardo Saffi Marques
2009-01-23  3:04 ` Volker Armin Hemmann
2009-01-23  5:24   ` Dale
2009-01-23  7:44     ` KH
2009-01-23  7:51       ` Dirk Heinrichs
2009-01-23  7:53       ` Dale
2009-01-23  8:16         ` Dirk Heinrichs
2009-01-23  8:45           ` Dale [this message]
2009-01-23  8:54             ` Dirk Heinrichs
2009-01-23  9:24               ` Dale
2009-01-24  1:08               ` Man Shankar
2009-01-24  9:32                 ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=497983A3.4090209@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox