On Mon, Apr 25, 2016 at 04:11:02AM +1000, Andrew McGlashan wrote:
> systemd continues to cause much more trouble than it is worth for so
> many people -- I really wish it wasn't so, but it truly is so. :(
Since I started this thread, I might as well speak up here: I am very
aware of your feelings
On Wednesday 20 April 2016 15:49:00 Jonathan Dowland wrote:
> Anyway, in the past I've read some useful tips for using Systemd on this
> list, so here's the blog post should it be of any interest:
>
> https://jmtd.net/log/mount_on_demand_backups/
Thanks. Here's my small contribution for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Apr 25, 2016 at 04:11:02AM +1000, Andrew McGlashan wrote:
>
> On 24/04/2016 8:10 PM, Ansgar Burchardt wrote:
> > Could you please keep your cancer to lists where people are not expected
> > to follow a minimal code of conduct[1]?
>
> I call
On 04/24/2016 08:11 PM, Andrew McGlashan wrote:
> systemd continues to cause much more trouble than it is worth for so
> many people -- I really wish it wasn't so, but it truly is so. :(
You don't seem to understand the criticism that has been levelled at
your conduct here. Ansgar didn't ask you
On 20/04/16 20:44, John L. Ries wrote:
Thanks! I think we need to share more examples on how to use systemd
properly. A lot of the criticism stems from the simple fact that people
just need to learn what the new tools can do for them.
That would be an indication that systemd is non-intuitive
On 24/04/2016 8:10 PM, Ansgar Burchardt wrote:
> Could you please keep your cancer to lists where people are not expected
> to follow a minimal code of conduct[1]?
I call jelly fish on your entire post.
systemd continues to cause much more trouble than it is worth for so
many people -- I really
Hi Andrew,
Andrew McGlashan writes:
> Sadly this software version of
> cancer is planned to keep spreading.
Could you please keep your cancer to lists where people are not expected
to follow a minimal code of conduct[1]?
I'm sure that you will find the
On 21/04/2016 7:19 AM, Ansgar Burchardt wrote:
> Here is a quick example in an interactive shell:
>
> +---
> | # umount /boot; ls /boot
> | [empty]
> | # unshare -m
Wheezy seems to need:
# unshare -m /bin/bash
Jessie gives you the shell by default (perhaps your default).
Cheers
AndrewM
On 21/04/2016 5:44 AM, John L. Ries wrote:
>> Thanks! I think we need to share more examples on how to use systemd
>> properly. A lot of the criticism stems from the simple fact that people
>> just need to learn what the new tools can do for them.
>
> That would be an indication that systemd is
Am 20.04.2016 um 23:19 schrieb Ansgar Burchardt:
> I'm not sure you can achieve this via systemd's .mount units, although
> systemd itself also makes use of mount namespaces. For example, systemd
> uses them to provide a per-service /tmp, make /home unaccessible or only
> allowing read-only
On Wed, Apr 20, 2016 at 11:19:46PM +0200, Ansgar Burchardt wrote:
> I think using mount namespaces is a bit nicer solution for the problem:
...
> I'm not sure you can achieve this via systemd's .mount units, although
> systemd itself also makes use of mount namespaces. For example, systemd
> uses
Hi,
Jonathan Dowland writes:
> I just wrote a blog post about how to use Systemd to configure mount-on-demand
> filesystems, e.g. /backup (in my case). This was triggered by recent news in
> the UK that a major hosting provider had deleted all their customer VMs by
> accident by issuing something
On Wed, Apr 20, 2016 at 09:40:40PM +0200, Jochen Spieker wrote:
> Did you edit your blog post afterwards or did I just skim over your own
> rebuttal of the story? :)
No I named it as a hoax from the off -- the tell for me was that one of the
replies to the hoax post was a suggestion to use dd(1)
On Wed, Apr 20, 2016 at 01:44:07PM -0600, John L. Ries wrote:
> >Thanks! I think we need to share more examples on how to use systemd
> >properly. A lot of the criticism stems from the simple fact that people
> >just need to learn what the new tools can do for them.
>
> That would be an
Thanks! I think we need to share more examples on how to use systemd
properly. A lot of the criticism stems from the simple fact that people
just need to learn what the new tools can do for them.
That would be an indication that systemd is non-intuitive and poorly
documented, which has been my
Jochen Spieker:
> Jonathan Dowland:
>>
>> I just wrote a blog post about how to use Systemd to configure
>> mount-on-demand
>> filesystems, e.g. /backup (in my case). This was triggered by recent news in
>> the UK that a major hosting provider had deleted all their customer VMs by
>> accident by
Jonathan Dowland:
>
> I just wrote a blog post about how to use Systemd to configure mount-on-demand
> filesystems, e.g. /backup (in my case). This was triggered by recent news in
> the UK that a major hosting provider had deleted all their customer VMs by
> accident by issuing something like "rm
I just wrote a blog post about how to use Systemd to configure mount-on-demand
filesystems, e.g. /backup (in my case). This was triggered by recent news in
the UK that a major hosting provider had deleted all their customer VMs by
accident by issuing something like "rm -rf" - but they *also* got
18 matches
Mail list logo