Re: Why compiling.
- To: firstname.lastname@example.org
- Subject: Re: Why compiling.
- From: Celejar <email@example.com>
- Date: Tue, 31 Jul 2012 13:21:40 -0400
- Message-id: <firstname.lastname@example.org>
- In-reply-to: <20120711060502.GW5583@sid.nuvreauspam>
- References: <CAGWVfM=vWd6HVuuc2WYFSiQZexqr3NL9R7CnSH2+r_bj6MUryA@mail.gmail.com> <4FFC344B.email@example.com> <firstname.lastname@example.org> <20120710202246.GO5583@sid.nuvreauspam> <email@example.com> <20120711060502.GW5583@sid.nuvreauspam>
On Wed, 11 Jul 2012 09:05:02 +0300
Andrei POPESCU <firstname.lastname@example.org> wrote:
> On Ma, 10 iul 12, 22:50:02, Celejar wrote:
> > On Tue, 10 Jul 2012 23:22:46 +0300
> > Andrei POPESCU <email@example.com> wrote:
> > Not quite sure I get you - if my hypothetical router (running x86 HW,
> > not like my actual routers that run OpenWRT on arm, and that don't
> > have lots of extra MB to spare) needs a new kernel, I can just send over
> > a distro stock one;
> From where? Your network is down and your other machine runs on a custom
Plug the regular machine straight into the internet connection (cable
modem) and grab an appropriate kernel.
> > why should my work machine kernel need to be
> > appropriate for my router?
> A stock kernel should work for both. IMHO, even if you do use custom
> kernels, it's probably a good idea to keep a stock kernel around for
> backup and troubleshooting.
Certainly agree - I always keep at least one stock kernel installed.