Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Submission + - Why does openvz require SELINUX to be disabled?

Anomalyst writes: All the howto's document declare that openvz must have SELINUX disabled, but none of them explain why this is the case. The Audit2allow process seems to present a solution and I would feel a lot better if a virtual host tasked with running multiple guests pertaining to core functionality had SELINUX protecting it from rogue applications and users. Has anyone actually got openvz to run with SELINUX running?

Comment If they dont like what I do with AdBlock - (Score 1) 686

They must really be shiating their silky little thong panties with what Ghostery and noscript does to their tattletale code. If they have a worthwhile product I'll hear it through word of mouth or an honest report in /. or Fark. They dont use their tools responsibly, with blinking and flashing and loops that you cant disable. So I deny them the right to reach me at all. When hell freezes over and they make appropriate and considerate use of their access to me, mebbe I'll turn it off. Until then I will show them the same lack of consideration and appropriateness.

Comment Re:No (Score 1) 388

That's an Ubuntu issue, mainly.

Not really, there's no PPA for RC4. Installation was by git clone & git pull,config, make, make install. I also tried from the tarball, same result no such file for the library import. I'm sure it'll sort out when they start building the .deb, but it doesn't do me any good now, nor does it allow me to help test the RC since I can get it to provision a new domain.

Comment Re:No (Score 2) 388

I saw that, it doesn't provide a solution, the file is not in the latest git pull nor in the tarball download. If I was really ambitious I gues I could start downloading & searching prior tarballs, but that really should not have to be done. It would be nice to know what source files generate the library. I have a sneaking suspicion they have renamed, as they did with the "provision" command and the code/library is really there, just not with the name in the import statement. I went through all the names with 'kdc' in them and it was not intuitively obvious that any of them correlated with the policy library. I am not stupid and tried really hard to use other avenues to resolve the issue before p*ssing and moaning, I would imagine things will get better once they start making a .deb package. At this point, the only PPA's I could find were for the alpha releases, sigh. I am really surprised there are not yum/apt/etc nightly packages available. Automating the package release seems like a no-brainer for either the SAMBA or Ubuntu team.

Slashdot Top Deals

"Of course power tools and alcohol don't mix. Everyone knows power tools aren't soluble in alcohol..." -- Crazy Nigel