You are not logged in.
Pages: 1
I get this message while booting and am wondering if anyone knows how to correct the problem.
Not activating Mandatory Access Control now since /sbin/tomoyo-init doesn't exist.
I haven't found any solutions or much explanation of what it is using google.
~trc
Offline
Does it still boot successfully? If it does check to see if /sbin/tomoyo-init actually exists. Maybe you installed tomoyo wrong? Here is the wiki page: https://wiki.archlinux.org/index.php/Tomoyo
I haven't found any solutions or much explanation of what it is using google.
If you don't know what it is, does that mean you did not realize you had it or somehow installed it by accident? If you did, just uninstall tomoyo. I think the package is called tomoyo-tools. Don't know if any of what I said will actually fix the problem as I don't use tomoyo...
Hope that helps.
I don't suffer from insanity. I enjoy every minute of it.
MSI CR600 / 3GB Memory / 320GB HDD / Intel Pentium Dual-Core CPU T4200 @ 2.00 GHz | Archlinux x86_64
Offline
/sbin/tomoyo does not exist on my system, and I don't remember ever having it, and yes my system still boots fine, I guess I'll try installion the tomoyo-tools
~trc
Offline
/sbin/tomoyo does not exist on my system
Your error message says /sbin/tomoyo-init...
ᶘ ᵒᴥᵒᶅ
Offline
I have the same error on all 3 of my Arch machines since installing 2.6.36 and also don't remember ever installing tomoyo*. There is also nothing in my pacman.log to suggest I ever had any tomoyo files installed. All my systems boot just fine though.
Offline
I suspect we are all getting it:
Nov 30 21:13:59 localhost kernel: TOMOYO Linux initialized
Nov 30 21:13:59 localhost kernel: Not activating Mandatory Access Control now since /sbin/tomoyo-init doesn't exist.
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
I suppose this is related to TOMOYO support being enabled in the Arch kernels now:
Offline
This is an old problem. I experienced a similar message some years ago with an Mandriva installation.
It is usually totally safe to ignore this message.
To know or not to know ...
... the questions remain forever.
Offline
I was wondering the same thing. Glad to know it's nothing problematic.
Offline
When I read the message I felt brave enough to try installing this mysterious tomoyo-tools, system boots fine like I didn't have it and it's happened about for a week. I forgot to have installed that.
Today my machine have had strange message and didn't boot, I've tried the fallback and the first time has worked. From fallback I have reinstalled tomoyo-tools, thinking some upgrade could have broken the package.
Well, reboot the machine and system still not booting, neither fallback this time. WTH!
I've used the livecd to move the binary /sbin/tomoyo-init (yes of course I can chroot and pacman -R but moving the binary was enough), booting correctly and pacman -R it.
The last message written was about kernel start etc, and the system stuck.
Offline
removed
Last edited by oupsemma (2011-01-17 12:18:03)
Offline
Aww sorry mates, it was just a kernel panic that don't has nothing to do with tomoyo. I really don't know if the panic has been made by the activity of tomoyo, I just know that I don't put the hands into my installation and the only last one action I've done is installing this package. To fix I've just reinstalled kernel26 with pacman from a chrooted livecd. I've check the filesystem nothing has been found. I don't know this strange reasonless kernel panic, I follow repository, so my kernel was regularly updated days ago.
@oupsemma I guess we don't care about your post because we have PKGBUILD and conflicts(), at least for the first point.
Now I try reinstalling tomoyo-tools, let's see if my kernel panic again.
Offline
Pages: 1