From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] alternative kernels
Date: Mon, 03 Nov 2014 00:46:34 +0000 [thread overview]
Message-ID: <1456111.TU6pHrz4dr@wstn> (raw)
In-Reply-To: <CAOdo=SwP2=OGw4xO-Hkmzj4uGKR5UgETLHnPArwiAF7tEW03Lw@mail.gmail.com>
On Sunday 02 November 2014 18:05:29 Tom H wrote:
> On Fri, Oct 31, 2014 at 12:16 PM, Peter Humphrey
> > > My grub-0.99 lets me choose from four kernels and two or three run
levels
> > at boot time, and grub-2 can't handle this yet, or it couldn't the last
> > time I checked. I don't suggest that everyone has a similar need, but at
> > least in some cases the old grub does still have a place.
>
> You can edit "/etc/grub.d/10_linux" to add more than the regular and
> the recovery entries.
>
> You can also "chmod -x" the files in "/etc/grub.d/*" and create manual
> entries in 40_custom (and keep it executable!).
Seems like there are more ways to skin the cat than I could shake a stick at
(apologies for the mixed metaphors).
--
Rgds
Peter
next prev parent reply other threads:[~2014-11-03 0:46 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 19:09 [gentoo-user] alternative kernels Alexander Kapshuk
2014-10-26 19:23 ` Canek Peláez Valdés
2014-10-26 19:40 ` Alexander Kapshuk
2014-10-26 20:20 ` Rich Freeman
2014-10-26 20:45 ` Canek Peláez Valdés
2014-10-26 20:33 ` Giuseppe Pappalardo
2014-10-26 19:41 ` Canek Peláez Valdés
2014-10-26 19:43 ` Canek Peláez Valdés
2014-10-26 20:56 ` Giuseppe Pappalardo
2014-10-26 19:47 ` Volker Armin Hemmann
2014-10-26 19:52 ` Alexander Kapshuk
2014-10-26 19:56 ` Alec Ten Harmsel
2014-10-26 20:16 ` Canek Peláez Valdés
2014-10-26 20:21 ` Alexander Kapshuk
2014-10-26 20:42 ` Alan McKinnon
2014-10-26 20:48 ` Alexander Kapshuk
2014-10-26 20:46 ` Canek Peláez Valdés
2014-10-26 20:49 ` Alexander Kapshuk
2014-10-26 21:01 ` Volker Armin Hemmann
2014-10-26 21:16 ` Canek Peláez Valdés
2014-10-26 23:18 ` Volker Armin Hemmann
2014-10-26 23:41 ` Canek Peláez Valdés
2014-10-27 1:12 ` wabenbau
2014-10-27 1:35 ` Alec Ten Harmsel
2014-10-27 1:54 ` wabenbau
2014-10-29 19:08 ` Matti Nykyri
2014-10-26 21:34 ` Rich Freeman
2014-10-26 21:10 ` Alec Ten Harmsel
2014-10-26 21:23 ` Canek Peláez Valdés
2014-10-26 21:48 ` Alan McKinnon
2014-10-26 23:25 ` Volker Armin Hemmann
2014-10-30 7:56 ` J. Roeleveld
2014-10-30 10:31 ` Rich Freeman
2014-10-31 6:30 ` J. Roeleveld
2014-10-31 6:37 ` Canek Peláez Valdés
2014-10-31 7:11 ` J. Roeleveld
2014-10-31 8:22 ` Canek Peláez Valdés
2014-10-31 9:42 ` Gregory Woodbury
2014-10-31 11:05 ` Tanstaafl
2014-10-31 14:09 ` J. Roeleveld
2014-10-31 16:16 ` Peter Humphrey
2014-10-31 17:24 ` Volker Armin Hemmann
2014-10-31 17:53 ` Rich Freeman
2014-10-31 20:26 ` Neil Bothwick
2014-11-01 11:19 ` Peter Humphrey
2014-11-01 15:38 ` Neil Bothwick
2014-11-01 17:19 ` Peter Humphrey
2014-11-01 22:28 ` Neil Bothwick
2014-11-02 13:14 ` Volker Armin Hemmann
2014-11-02 15:28 ` Neil Bothwick
2014-11-03 2:09 ` Tom H
2014-11-03 8:36 ` Neil Bothwick
2014-11-02 23:05 ` Tom H
2014-11-03 0:46 ` Peter Humphrey [this message]
2014-11-03 2:26 ` Tom H
2014-10-31 22:09 ` Tom H
2014-10-31 22:30 ` Rich Freeman
2014-11-01 1:03 ` Alec Ten Harmsel
2014-11-01 9:47 ` Rich Freeman
2014-11-01 15:50 ` Alec Ten Harmsel
2014-11-03 1:54 ` Tom H
2014-11-03 1:40 ` Tom H
2014-11-03 0:22 ` Tom H
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=1456111.TU6pHrz4dr@wstn \
--to=peter@prh.myzen.co.uk \
--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