Steven Lembark lembark at wrkhors.com writes:
Solution that works for me:
- Compile the kernel with everything built-in leaving modules for the
few things that really need to be reloadable. Turn everything in
the bloody thing off. This avoids the need for a kernel-specific
Neil Bothwick neil at digimed.co.uk writes:
So if I do this, what will I have to do to keep the system booting.
Nothing, I installed r7 on June 26th and the system just kept booting.
You can run grub-install if you really want to, but as this is a patch
level update to the same version,
On Fri, Jul 17, 2015 at 08:36:51AM +0100, Neil Bothwick wrote:
could try it on. But it's a headless MythTV backend in the loft, so
there will be fun and games if it doesn't boot.
Wouldn't it be more accurate to say there will be _no_ fun and games if
it doesn't boot?
--
wraeth
On Thu, 16 Jul 2015 19:54:31 -0400, Jonathan Callen wrote:
The Gummiboot project is no longer maintained, it has been merged into
systemd as systemd-boot (note that using any other part of Systemd
should *not* be required to use systemd-boot, but I don't know for
sure because I do not have
On Fri, Jul 17, 2015 at 10:40:16AM +0100, Neil Bothwick wrote:
On Fri, 17 Jul 2015 18:45:59 +1000, wraeth wrote:
could try it on. But it's a headless MythTV backend in the loft, so
there will be fun and games if it doesn't boot.
Wouldn't it be more accurate to say there will be
On Fri, 17 Jul 2015 18:45:59 +1000, wraeth wrote:
could try it on. But it's a headless MythTV backend in the loft, so
there will be fun and games if it doesn't boot.
Wouldn't it be more accurate to say there will be _no_ fun and games if
it doesn't boot?
Well, with no TV to watch, I'd
Alan McKinnon alan.mckinnon at gmail.com writes:
The don't use it, grub:0 still works just fine
It's all working fine (atm). But changes are problematic, or at least
they have been in the past
I gave grub-2 a try earlier this week and once again couldn;t figure out
how to install that
Alec Ten Harmsel alec at alectenharmsel.com writes:
Grub-2.02_beta2-r3 wants to upgrade to grub-2.02_beta2-r7
It looks like he’s going from grub-2.02 to grub-2.02. I don’t think
any action is necessary.
Notice r3-- r7
Grub 2 can be a bear in sheep's clothing
I know that for
Solution that works for me:
- Compile the kernel with everything built-in leaving modules for the
few things that really need to be reloadable. Turn everything in
the bloody thing off. This avoids the need for a kernel-specific
filestem in the initrd.
- This since you don't need
Am 16.07.2015 um 22:05 schrieb James:
I spent days during early kernel upgrades getting grub2 happy.
You only need to run `grub2-mkconfig -o /boot/grub/grub.cfg` after each
kernel update. I'm using grub2 not for such a long time, but I made some
kernel upgrades since I switched from grub-legacy
Jarry mr.jarry at gmail.com writes:
I have similar setup as you and upgraded grub without any
problem. If beta2-r3 worked for you, beta2-r7 will as well.
If you did not disable /boot automount, there are no special
steps needed. Portage will mount /boot, update grub, and
dismound
On 16-Jul-15 22:08, James wrote:
I have similar setup as you and upgraded grub without any
problem. If beta2-r3 worked for you, beta2-r7 will as well.
If you did not disable /boot automount, there are no special
steps needed. Portage will mount /boot, update grub, and
dismound afterwards...
On Thu, 16 Jul 2015 20:01:29 + (UTC), James wrote:
I gave grub-2 a try earlier this week and once again couldn;t figure
out how to install that mini-OS that bootstraps a boot loader which
bootstraps a boot loader which loads code that loads a kernel. So back
to grub:0 for me
I do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2015-07-16 17:41, Neil Bothwick wrote:
On Thu, 16 Jul 2015 20:01:29 + (UTC), James wrote:
I gave grub-2 a try earlier this week and once again couldn;t
figure out how to install that mini-OS that bootstraps a boot
loader which
14 matches
Mail list logo
