The diff has about 6k lines.
On Thu, Apr 28, 2011 at 5:19 AM, Kay Sievers wrote:
> On Wed, Apr 27, 2011 at 17:32, DR wrote:
> > Er..As I explained above, this problem just exists with my customized
> kernel
> > and
> > not with the archlinux official kernel. So I asked 'what kernel options
>
The reason I limited it to just D or x is that without that, r and R files
would also be protected and that wouldn't be desired. I can do a check just
for those however since unfiltered behavior otherwise makes more sense.
On Apr 27, 2011 12:52 PM, "Lennart Poettering"
wrote:
On Wed, 27.04.11 1
On Mon, 04.04.11 18:30, Albert Strasheim ([email protected]) wrote:
>
> Hello
>
> On Mon, Apr 4, 2011 at 6:01 PM, Albert Strasheim wrote:
> > I'm trying to set up a configuration where a variable number of
> > devices under /dev/mapper get automounted.
> > I've started with the following:
> > #
On Wed, Apr 27, 2011 at 17:32, DR wrote:
> Er..As I explained above, this problem just exists with my customized kernel
> and
> not with the archlinux official kernel. So I asked 'what kernel options are
> required'.
> I didn't mean that it is a bug in systemd.
If you diff the kernel .config fil
On Wed, 27.04.11 10:03, William Douglas ([email protected]) wrote:
>
> +static bool protected(const char *key) {
> +struct Item *i;
> +
> +if (!(i = find_glob(globs, key)))
> +if (!(i = (Item *)hashmap_get(items, key)))
> +return
Below is version 3 of tmpfile white listing.
>From ed06da9a9dea18070cedf0bc2bf3d387b1bd57f0 Mon Sep 17 00:00:00 2001
From: William Douglas
Date: Tue, 19 Apr 2011 15:12:19 -0700
Subject: [PATCH] Implement tmpfile white listing.
x, in addition to its old behavior, now will protect (recursively)
f
On Wed, 27.04.11 23:32, DR ([email protected]) wrote:
> Er..As I explained above, this problem just exists with my customized kernel
> and
> not with the archlinux official kernel. So I asked 'what kernel options are
> required'.
> I didn't mean that it is a bug in systemd.
But this doesn't
Er..As I explained above, this problem just exists with my customized kernel
and
not with the archlinux official kernel. So I asked 'what kernel options are
required'.
I didn't mean that it is a bug in systemd.
--
Dark Raven
-Waiting for chaos to begin
On Wed, Apr 27, 2011 at 11:16 PM, Lennart
On Wed, 27.04.11 22:46, [email protected] ([email protected]) wrote:
> I recently started to use systemd. But I experienced a very annoying
> problem. When I try 'systemctl poweroff', everything goes fine first,
> systemd says 'Detaching DM Device' and exits, the kernel stopped my
> hard d
I recently started to use systemd. But I experienced a very annoying
problem. When I try 'systemctl poweroff', everything goes fine first,
systemd says 'Detaching DM Device' and exits, the kernel stopped my
hard disk and disabled non-boot cpus, but then my computer just hang
there. I wait for about
On Wed, 27.04.11 02:07, Cristi Patty ([email protected]) wrote:
> in [manager.c], function [manager_reload], close to the end of
> function, there are these lines:" assert(m->n_deserializing >
> 0); m->n_deserializing ++; "- is it
> really OK the " m->n
in [manager.c], function [manager_reload], close to the end of function, there
are these lines:" assert(m->n_deserializing > 0);
m->n_deserializing ++; "- is it really OK the
" m->n_deserializing ++ " or it should have been " m->n_deserializing -- " ?
Tha
Hi,
2011/4/27 Lennart Poettering :
> I would suggest to leave the parsing of the fsck -C output to fsckd, as
> well as the integration of multiple of these streams. fsckd would then
> only pass one stream of progress bar information to plymouth. The
> handling in Plymouth would be very simple: you
13 matches
Mail list logo
