unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Help with auto-mounting a specific file-system.
Date: Mon, 20 Apr 2020 09:39:27 -0400	[thread overview]
Message-ID: <20200420093927.42e9608f.raghavgururajan@disroot.org> (raw)
In-Reply-To: <87zhb6jxfz.fsf@ambrevar.xyz>


> To clarify, you can configure udisks to mount your drives somewhere else
> like your home directory.

Ah I see. Btw, guix does not use udisks to mount file-systems right?

Like mounting root file-system at "/", guix just uses mount command correct?

> Udiskie is a user service, so I don't think it makes sense to include it
> in udisks-service-type.

Oh. I have to read about types of services then. As a guess, is it the
difference between service running 'system-wide' and 'as and for that user'?

> But you can run shepherd as user.  I have this service:
> 
> --8<---------------cut here---------------start------------->8---
> (define auto-mount
>   (make <service>
>     #:provides '(auto-mount)
>     #:start (make-system-constructor "udiskie &")
>     #:stop (make-system-destructor "pkill udiskie")
>     #:respawn? #t))
> --8<---------------cut here---------------end--------------->8---

Thanks so much. Just to double check, should I put this in my config.scm?

Regards,
RG.

  reply	other threads:[~2020-04-20 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  6:37 Help with auto-mounting a specific file-system Raghav Gururajan
2020-04-20  9:15 ` Pierre Neidhardt
2020-04-20  9:22 ` Raghav Gururajan
2020-04-20  9:29   ` Pierre Neidhardt
2020-04-20  9:42   ` Raghav Gururajan
2020-04-20  9:52     ` Pierre Neidhardt
2020-04-20 13:39       ` Raghav Gururajan [this message]
2020-04-20 14:32         ` Pierre Neidhardt
2020-04-20 19:45 ` Michael Rohleder

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20200420093927.42e9608f.raghavgururajan@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).