unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Help with auto-mounting a specific file-system.
Date: Mon, 20 Apr 2020 09:42:12 +0000	[thread overview]
Message-ID: <1e1aaec3b2fd14c13fe57d03d4940bc1@disroot.org> (raw)
In-Reply-To: <87k12ald2w.fsf@ambrevar.xyz>

Hi Pierre!
 
> I think the best way to do this is to use Guix to set the right Udev
> rules for Udisks:
> 
> https://wiki.archlinux.org/index.php/Udisks

I thought I could use the same concept of mounting /home or /boot or /store etc., from another disk. But all these are immediately after root directory "/" and are likely to be protected. So then I should not be using this technique to mount something under user's directory "~/".

Okay, no problem. I can just do git operations by 'cd'ing to /media/foo/bar, which is mounted by udisks/udiskie.

Now, I am would like to modify udisks-service-type, to include an option like `enable-udiskie? boolean` in udisks-configuration. If it is #t, udiskie will run along with udisks service, on every start-up. Could you help me with a scheme code to achieve this?

Btw, this is not just for me. We can patch it in guix. This will be very handy for folks using light-weight DE or window-managers. :-)

Regards,
RG.

  parent reply	other threads:[~2020-04-20  9:42 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 [this message]
2020-04-20  9:52     ` Pierre Neidhardt
2020-04-20 13:39       ` Raghav Gururajan
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=1e1aaec3b2fd14c13fe57d03d4940bc1@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).