Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #267557

sudo udisksctl

From Max Nikulin <manikulin@gmail.com>
Newsgroups linux.debian.user
Subject sudo udisksctl
Date 2024-02-18 04:30 +0100
Message-ID <I8G2l-aTcf-3@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


I have decided to ask the following in a separate thread.

On 17/02/2024 02:59, David Wright wrote
(Re: f3tools vs Silicon Power 4T drive):
>   lulu () 
>   { 
>     sudo udisksctl unlock --block-device /dev/disk/by-partlabel/Lulu01 && mount /media/lulu01
>   }

I am evaluating if udisks2 D-Bus API allows to create a tool as 
convenient as pmount(1) that is smart enough to unlock a device before 
mounting it (optionally with specified name of mountpoint)

     pmount /dev/sda1 mybackup

I have puzzled by your function however. I believed that udisks was 
created to allow *regular* users to mount drives. If you are using sudo 
why do not you use "cryptsetup open" directly? Otherwise udisksctl can 
ask password if policy does not allow disk operations for the current user.

P.S. Unfortunately mount name is hardcoded in udisksd. It is either 
label or UUID, it can not be specified when a partition is mounted.

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

sudo udisksctl Max Nikulin <manikulin@gmail.com> - 2024-02-18 04:30 +0100
  Re: sudo udisksctl David Wright <deblis@lionunicorn.co.uk> - 2024-02-18 05:50 +0100
    Re: sudo udisksctl Max Nikulin <manikulin@gmail.com> - 2024-02-18 06:50 +0100
      Re: sudo udisksctl David Wright <deblis@lionunicorn.co.uk> - 2024-02-19 05:40 +0100
        Re: sudo udisksctl Max Nikulin <manikulin@gmail.com> - 2024-02-19 18:00 +0100
          Re: sudo udisksctl David Wright <deblis@lionunicorn.co.uk> - 2024-02-21 19:50 +0100

csiph-web