public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rabi Shanker Guha <guha.rabishankar@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] netifrc on systemd: Weekly Report #5
Date: Sun, 22 Jun 2014 19:58:49 +0530	[thread overview]
Message-ID: <CAJGtUJLspBXswn2boQU3KxP4m7eHT=3J0Y7eGJtJy8R-+0mXYA@mail.gmail.com> (raw)
In-Reply-To: <861tuhzdqo.fsf@moguhome00.in.awa.tohoku.ac.jp>

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

Hello Benda,

Actually this is not my convention. This is piggybacking on the systemd
convention
In the current system (openrc) net.eth0 is a symlink to net.lo and the
interface is deduced at run-time and appropriate action is taken.
In systemd instantiated services work in the same way. Symlink to the
original service and the @ part is passed as a parameter and I guess it is
supposed to be used the same way too i.e. the @ part is to be  seen as an
variable. So I thought this would be the best way to represent it in
systemd setting.

Hope this makes sense.


On Sun, Jun 22, 2014 at 11:29 AM, <heroxbd@gmail.com> wrote:

> Hey Rabi,
>
> Rabi Shanker Guha <guha.rabishankar@gmail.com> writes:
>
> > sudo systemctl restart net@eth0
> > sudo systemctl status net@eth0
>
> Just curious how this naming scheme were formed. Intuitively, eth0 is a
> subset of net, making "eth0@net" and "net.eth0" more natural.
>
> Benda
>
>


-- 
Regards,
Rabi

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

      reply	other threads:[~2014-06-22 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22  5:50 [gentoo-soc] netifrc on systemd: Weekly Report #5 Rabi Shanker Guha
2014-06-22  5:59 ` heroxbd
2014-06-22 14:28   ` Rabi Shanker Guha [this message]

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='CAJGtUJLspBXswn2boQU3KxP4m7eHT=3J0Y7eGJtJy8R-+0mXYA@mail.gmail.com' \
    --to=guha.rabishankar@gmail.com \
    --cc=gentoo-soc@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox