On 2/6/26 8:58 PM, Tim via users wrote:
On Fri, 2026-02-06 at 13:33 -0800, Paolo Galtieri wrote:
This is an NTFS drive so SElinux permissions shouldn't apply. Plus
/run/media/pgaltieri/SDNVIRTLAB06/
is mounted when I login. If there where SElinux issues I would expect
Yes, and no...
SELinux can still be involved in imposing restrictions on you, but NTFS
(and other filesystems, too) do not have any way of storing any SELinux
meta information that allows different access restrictions. So very
basic default permissions are being used, and are probably too
restrictive for your needs.
I was finally able to create my first VM on F43, but it is more
complicated than with VMware or VirtualBox. Specifically the first
running of virt-manager has to be done under sudo. This is so it
corrects permission issues. If you run virt-manager as a regular user
it complains about access and asks if you want to fix it, but if you
answer yes it fails with permission denied. So the issues seem more to
be about libvirt permissions than about SElinux issues since I didn't
get any SElinux alerts after creating my VM.
Now if I can only fix my Ubuntu system I'd be happier. Anyone know
how to fix the following?
error: insmod isn't allowed to execute in an extractor
I get about 9 total of these messages though not all the same.
This happens when I try to boot an alternate kernel from grub shell
after running
extract_entries_configfile /boot/grub/grub.cfg
The problem I'm having where I need to do this is because I noticed
Ubuntu does not have SElinux installed. So I removed AppArmor and
tried to install SElinux. This hangs. Somehow during the process of
trying to install SElinux I no longer see the grub boot menu. Since I
modified the kernel command line to relabel the fs for SElinux I can
no longer edit the command line to remove the SElinux parameter so
when the system boots it starts to relabel and it hangs.
Since this is a grub issue and not a Ubuntu issue I'm hoping someone
here can give me suggestions on how to fix it.
Paolo
I have F43 installed in a VM on F43 to test newer kernel versions to
test for support for Mediatek 7927 wireless chipsets which unusually are
not supported yet. By default I found that when I ran virt-manager the
first time to install the guest system I had to run it under sudo.
Having install the guest I also found that every time I ran virt-manager
I had to run it under sudo, until I added my userid to the libvirt group
and now I don't have to run it under sudo anymore. I haven't tried
installing another guest like Ubuntu as yet to see if that still works.
I used to boot between Windows 11, Fedora and Ubuntu but I was doing
that by using Fedora's grub menus. Having said this though, like under
Fedora, I used to build the grub menus in Ubuntu by using the
grub2-mkconfig command, and if I configured my motherboard bios to boot
from Ubuntu instead of from Fedora, I had no issues with the Ubuntu grub
menus being displayed. The only issue I had with the Ubuntu grub menus
was the entry created to boot Fedora would fail with SHIM errors.
I might be treading on thin ice here, but in my view Ubuntu not having
Selinux is an advantage. The number of times I've had Selinux messages
pop up that had nothing to do with the software I was running at the
time, and to me were for things that were a standard part of Fedora as
opposed to being relative to software I had explicitly installed that
was external to the repositories, was nothing more than a pain that
shouldn't be required.
Why do you need to run the extract command to see the grub menus, or
have I misinterpreted what you were saying?
regards,
BEGIN:VCARD
VERSION:4.0
N:Morris;Stephen;;;
FN:Stephen Morris
EMAIL;PREF=1;TYPE=home:[email protected]
END:VCARD
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
