gnupic: Re: [gnupic] Fwd: [Bug 132141] kernel doesn't know its own name--Best OS for gnupic
Subject:
Re: [gnupic] Fwd: [Bug 132141] kernel doesn't know its own name--Best OS for gnupic
From:
Dan Andersson ####@####.####
Date:
12 May 2006 23:18:43 +0100
Message-Id: <200605122318.41054.dan@andersson.co.uk>
And why pissing about with Linux at all when there is FreeBSD?
The Important thing is that the operating system should be secondary to the
apps we want to run. At the very moment the operating system or different
Linux variants makes a difference, it's eith a flawed app or a flawed OS.
You need to make a choice, play with the kernels or do some work with PIC's...
If the OS is good enough to run the apps - it's subsequently not broken.
If it's not broken, don't mend it...
That's a full £ of my thoughts, not just 0.02 Cents
Cheers
Dan / M0DFI
On Friday 12 May 2006 21:18, Samuel Leathers wrote:
> just a suggestion, but if you are more interested in programming
> microchips than playing with linux kernels, why gentoo? I'd recommend
> something easy to setup and maintain like ubuntu, and then get code from
> cvs and compile manually.
>
> my .02 cents
>
> Sam
>
> > On 5/12/06, Marco Pantaleoni ####@####.####
> >
> > If "uname -a" says it's 2.6.12, it's very, very probable it's 2.6.12.
> > If you want to be even more sure, please do a "cat /proc/version".
> > This gets the version directly from the live kernel, so...
> > IMHO you have compiled the new kernel, but forgot to reconfigure or
> > misconfigured your boot loader (what do you use? lilo, grub, others?
> > Have you added a new stanza to lilo and re-run lilo? Or modified grub
> > configuration file?)
> >
> > Ciao,
> > Marco
> >
> >
> > I boot from the grub prompt. Not going to write a conf file until the
> > thing
> > is up and running the way I like.
> >
> >> --
> >> Marco Pantaleoni
> >>
> >> elastiC language developer
> >> http://www.elasticworld.org
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: ####@####.####
> >> For additional commands, e-mail: ####@####.####
