On 11 Mar 2013 02:30, Kevin Kofler kevin.kof...@chello.at wrote:
Lennart Poettering wrote:
True thing. libselinux is a library we really really should avoid
linking against.
Why the sarcasm? SELinux and libselinux only ever cause problems, why
can't
we finally kick them out of Fedora?
On Sun, Mar 10, 2013 at 10:28 PM, Kevin Kofler kevin.kof...@chello.at wrote:
Why the sarcasm? SELinux and libselinux only ever cause problems, why can't
we finally kick them out of Fedora?
I find them very useful on my systems, and I think it's a bit extreme
to say that they only ever cause
On Mon, Mar 11, 2013 at 03:28:47AM +0100, Kevin Kofler wrote:
Lennart Poettering wrote:
True thing. libselinux is a library we really really should avoid
linking against.
Why the sarcasm? SELinux and libselinux only ever cause problems, why can't
we finally kick them out of Fedora?
This
On 11/03/13 22:57, Richard W.M. Jones wrote:
On Mon, Mar 11, 2013 at 03:28:47AM +0100, Kevin Kofler wrote:
Lennart Poettering wrote:
True thing. libselinux is a library we really really should avoid
linking against.
Why the sarcasm? SELinux and libselinux only ever cause problems, why can't
Lennart Poettering wrote:
True thing. libselinux is a library we really really should avoid
linking against.
Why the sarcasm? SELinux and libselinux only ever cause problems, why can't
we finally kick them out of Fedora?
Kevin Kofler
--
devel mailing list
On 03/04/2013 07:05 PM, Lennart Poettering wrote:
On Mon, 04.03.13 10:24, David Highley (dhigh...@highley-recommended.com) wrote:
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com) wrote:
Twice now we have one Fedora 18 system where systemd
On Wed, 06.03.13 06:55, Steve Clark (scl...@netwolves.com) wrote:
On 03/04/2013 07:05 PM, Lennart Poettering wrote:
On Mon, 04.03.13 10:24, David Highley (dhigh...@highley-recommended.com)
wrote:
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley
On 03/06/2013 07:08 AM, Lennart Poettering wrote:
On Wed, 06.03.13 06:55, Steve Clark (scl...@netwolves.com) wrote:
On 03/04/2013 07:05 PM, Lennart Poettering wrote:
On Mon, 04.03.13 10:24, David Highley (dhigh...@highley-recommended.com) wrote:
Lennart Poettering wrote:
On Mon, 04.03.13
Steve Clark (scl...@netwolves.com) said:
Well you can be as sarcastic as you want but I have been using UNIX/Linux
since 1985 and never had init hang or die on me.
sysvinit and systemd have linked against libselinux since SELinux policy was
introduced. upstart only didn't because policy was
On 03/05/2013 04:02 AM, David Highley wrote:
Unlike the bug report which indicates you can to a sync reboot,
nothting but the power switch gets this system out of the issue.
Did you use the -f switch?
sync reboot -f
Michal
--
devel mailing list
devel@lists.fedoraproject.org
Michal Schmidt wrote:
On 03/05/2013 04:02 AM, David Highley wrote:
Unlike the bug report which indicates you can to a sync reboot,
nothing but the power switch gets this system out of the issue.
Did you use the -f switch?
sync reboot -f
Missed the the -f switch. Will give it a try if
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and we're not able to do an init 6 to restart the system.
Did notice today that a full process list showed a message about abrt
and something to the
On Mon, Mar 04, 2013 at 07:56:51AM -0800, David Highley wrote:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and we're not able to do an init 6 to restart the system.
Did system logs or dmesg
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com) wrote:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and we're not able to do an init 6 to restart the system.
Did
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com)
wrote:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and we're not able to do an init 6
David Highley wrote:
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com)
wrote:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and
On Mon, 04.03.13 10:24, David Highley (dhigh...@highley-recommended.com) wrote:
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com)
wrote:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive
Lennart Poettering wrote:
On Mon, 04.03.13 10:24, David Highley (dhigh...@highley-recommended.com)
wrote:
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com)
wrote:
Twice now we have one Fedora 18 system where systemd seems
18 matches
Mail list logo
