mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Raphael Cohn <raphael.cohn@stormmq.com>
To: musl@lists.openwall.com
Subject: Re: _PATH_LASTLOG
Date: Tue, 3 Dec 2013 20:52:38 +0000	[thread overview]
Message-ID: <CACCP0GqBA5arWDstu58eFiYs2JKmD38Vrkn3Jcj8xbLz6gKeVg@mail.gmail.com> (raw)
In-Reply-To: <529E4437.8060706@skarnet.org>

[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]

Linking /etc to something in /var was what we were going to do...

Raphael Cohn
Chief Architect, stormmq
Co-Chair, OASIS MQTT Standard
Secretary, OASIS AMQP Standard
raphael.cohn@stormmq.com
+44 7590 675 756

UK Office:
Hamblethorpe Farm, Crag Lane, Bradley BD20 9DB, North Yorkshire, United
Kingdom
Telephone: +44 845 3712 567

Registered office:
16 Anchor Street, Chelmsford, Essex, CM2 0JY, United Kingdom
StormMQ Limited is Registered in England and Wales under Company Number
07175657
StormMQ.com


On 3 December 2013 20:51, Laurent Bercot <ska-dietlibc@skarnet.org> wrote:

>
>  What would be nice might be to be able to define the prefix for /etc to
>> something else (so we can use atomic symlink changes to flip configs).
>>
>
>  Make /etc a symlink to /var/config/etc. Make /var/config a symlink to
> config-0.
> Flip configs by atomically replacing the /var/config symlinks.
>  You'll have to move /etc, or part of it, out of the root filesystem
> anyway, because
> you'll want to make your / read-only: so, kill two birds with one stone.
>
>
>
>  PS As an aside, I've always wanted /etc/hosts to also have a parallel
>> /etc/hosts.d/.
>>  It'd make maintaining things without a DNS server extremely easy - think
>> dynamically
>>  adding and removing VMs in most cloud providers, especially those where
>> multicast DNS
>>  doesn't work... like Azure.
>>
>
>  Honestly, using djbdns is almost as easy, thanks to the programmatically
> sane config
> file formats; and it will scale better.
>
> --
>  Laurent
>
>

[-- Attachment #2: Type: text/html, Size: 2467 bytes --]

  reply	other threads:[~2013-12-03 20:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 17:44 _PATH_LASTLOG Raphael Cohn
2013-12-03 18:42 ` _PATH_LASTLOG Szabolcs Nagy
2013-12-03 19:09   ` _PATH_LASTLOG Raphael Cohn
2013-12-03 19:54     ` _PATH_LASTLOG Rich Felker
2013-12-03 20:10       ` _PATH_LASTLOG Raphael Cohn
2013-12-03 20:25         ` _PATH_LASTLOG Rich Felker
2013-12-03 20:44           ` _PATH_LASTLOG Laurent Bercot
2013-12-03 20:51             ` _PATH_LASTLOG Raphael Cohn
2013-12-03 21:00               ` _PATH_LASTLOG Nathan McSween
2013-12-03 21:05                 ` _PATH_LASTLOG Raphael Cohn
2013-12-03 21:42                 ` _PATH_LASTLOG Rich Felker
2013-12-03 21:38             ` _PATH_LASTLOG Rich Felker
2013-12-03 20:49           ` _PATH_LASTLOG Raphael Cohn
2013-12-03 20:51         ` _PATH_LASTLOG Laurent Bercot
2013-12-03 20:52           ` Raphael Cohn [this message]
2013-12-03 19:34 ` _PATH_LASTLOG Rich Felker
2013-12-03 19:50   ` _PATH_LASTLOG Raphael Cohn
2013-12-03 20:03     ` _PATH_LASTLOG Laurent Bercot
2013-12-03 20:11       ` _PATH_LASTLOG Raphael Cohn
2013-12-03 20:06     ` _PATH_LASTLOG Rich Felker
2013-12-03 20:18       ` _PATH_LASTLOG Raphael Cohn
2013-12-03 20:30         ` _PATH_LASTLOG Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACCP0GqBA5arWDstu58eFiYs2JKmD38Vrkn3Jcj8xbLz6gKeVg@mail.gmail.com \
    --to=raphael.cohn@stormmq.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).