My question is - why? Shouldn't getty start automatically when I
attempt to access VT1?
I'll answer my own question. It's because I should be using 'systemctl
isolate' to change; not 'systemctl start'.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscriptio
I'm running CentOS 7 in QEMU-KVM just as a play area / test bed.
It boots up in multi-user.target and I can access all virtual terminals.
If I change to the graphical.target, then I see Gnome's login screen on
VT1 and console logins on others. If I now login using VT2 and go back
to multi-use
There's an argument for totally ignoring NVRAM. rEFInd, an EFI boot
manager, produces its boot entries dynamically from fstab, a static
configuration file, and the contents of /boot. It ignores NVRAM,
there's no constantly modified grub.cfg on the EFI system partition
when kernels are updated
On 11/07/14 06:24, Chris Murphy wrote:
On Jul 10, 2014, at 4:56 AM, "Williams, Gareth"
wrote:
My question therefore is: Does anaconda do something else after running
'efibootmgr' to make it permanent? Or: Why can anaconda update NVRAM using
efibootmgr, while I can't?
'no bootable device' s
