21 Aug
2012
21 Aug
'12
7:45 p.m.
On Tue, 21 Aug 2012 19:44:35 +0200, Kaj Ailomaa <zequence(a)mousike.me>
wrote:
On Tue, 21 Aug 2012 19:27:59 +0200, Ralf Mardorf
<ralf.mardorf(a)alice-dsl.net> wrote:
That should have read, "less complicated"
On Tue, 2012-08-21 at 19:21 +0200, Kaj Ailomaa
wrote:
I was just pointing out why deciding boot order between kernels may be
unneeded, if keeping -generic and -lowlatency on the same machine, as
they are more or less the same kernel.
Don't see how editing files manually, and installing legacy software On Tue, 21 Aug 2012 15:06:22 +0200, James Harkins
<jamshark70(a)gmail.com>
wrote:
Or else
- you simply edit grub.cfg manually, as I did
- you switch to grub legacy, as I did and edit menu.lst manually as I do
:p
Why making things unneeded complicated?
Regards,
Ralf
> From: "Kaj Ailomaa"
> To make linux-lowlatency default, I'd just not install
linux-generic at
> all.
Maybe overkill: grub-customizer lets you choose whichever installed
kernel you want to be the default.
Not overkill, since -lowlatency is a -generic, but with a different
configuration. Why keep -generic, if you don't need it for anything? makes things complicated compared to doing nothing at
all.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user