Re: linux-source-3.2.0-rc7

[lina <lina.lastname@gmail.com>]

On Thursday 05,January,2012 11:25 PM, Camaleón wrote:
> On Thu, 05 Jan 2012 14:38:23 +0800, lina wrote:
>
> > a quick question,
> >
> > Which header I should choose?
> >
> > linux-headers-3.2.0-rc7-all_3.2~rc7-1~experimental.1_amd64.deb
> This is a metapackage which includes all (for all of the available
> architectures) of the headers packages.
>
> > linux-headers-3.2.0-rc7-all-amd64_3.2~rc7-1~experimental.1_amd64.deb
> This is a metapackage which includes all (for all of the available
> architectures of amd64) of the headers packages.
>
> > linux-headers-3.2.0-rc7-amd64_3.2~rc7-1~experimental.1_amd64.deb
> Individual package headers for amd64 arch.
>
> > linux-headers-3.2.0-rc7-common_3.2~rc7-1~experimental.1_amd64.deb
> Commom files for headers (amd64 arch.)
>
> > linux-headers-3.2.0-rc7-rt-amd64_3.2~rc7-1~experimental.1_amd64.deb
> Individual package headers for amd64 arch and RT kernel.
>
> > what does the last one mean, rt?
> It should be for a _R_eal _T_ime kernel.
>
> Hum... wait. There is/was no "real time" kernels compiled for Debian
> unless this has changed recently :-?
>
> > and what's the difference among those,
> The difference is the type of kernel you are currently using and what
> kind of package do you need.
>
> > Thanks,
> >
> > $ uname -a
> > Linux debian 3.2.0-rc6-3.2-mj-lina #1 SMP Sat Dec 17 13:14:26 SGT 2011
> > x86_64 GNU/Linux
> >
> > the one I built from kernel.org a bit heavy, took so much space. I am
> > not sure if I built from debian repository whether it will be light,
> Mmmm... those kernel headers (compiled for 3.2.0-rc7) won't match your
> current and self-compiled kernel (3.2.0-rc6).
>
> Greetings,
I installed one, after reboot, it got kernel panic, even can't mount / 
and others.

so I just back to old old kernel and removed present one.

now I decided to download from kernel.org and do a try.

the kernel panic was caused due to my .config file or ?

I am also stuck in Warning messages as following: even for opening emails.

another thing is bad, my $ date
Mon Jan  1 08:26:27 SGT 2001

It's getting 11 years younger (not me). bad ... bad ... bad .. to the past.

This Connection is Untrusted





          You have asked Iceweasel to connect
securely to mail.google.com, but we can't confirm that your connection 
is secure.
          Normally, when you try to connect securely,
sites will present trusted identification to prove that you are
going to the right place. However, this site's identity can't be verified.



          What Should I Do?

            If you usually connect to
this site without problems, this error could mean that someone is
trying to impersonate the site, and you shouldn't continue.






          Technical Details




          I Understand the Risks

            If you understand what's going on, you
can tell Iceweasel to start trusting this site's identification.
Even if you trust the site, this error could mean that someone is
tampering with your connection.
            Don't add an exception unless
you know there's a good reason why this site doesn't use trusted 
identification.