How to change default permission for usb devices filesystem

 To change the default permissions for USB devices' filesystems in Linux, you can use a combination of udev rules and mounting options. Here's how to do it:


1. **Identify the USB Device**:

   Plug in the USB device and note its properties, such as the vendor ID and product ID. You can use the `lsusb` command to list connected USB devices and get this information.


2. **Create a Custom udev Rule**:

   You can create a custom udev rule to specify the permissions and ownership for the device when it's connected. For example, create a file in the `/etc/udev/rules.d/` directory, such as `/etc/udev/rules.d/99-usb-permissions.rules`, and add the following content:


   ```bash

   SUBSYSTEMS=="usb", ATTRS{idVendor}=="your_vendor_id", ATTRS{idProduct}=="your_product_id", MODE:="0666"

   ```


   Replace `"your_vendor_id"` and `"your_product_id"` with the actual values from the `lsusb` output for your USB device. The `MODE:="0666"` sets read and write permissions for everyone.


3. **Reload udev Rules**:

   After creating the custom rule, you need to reload the udev rules:


   ```bash

   sudo udevadm control --reload

   sudo udevadm trigger

   ```


4. **Unmount and Reconnect the USB Device**:

   Unmount the USB device (if it's already mounted), and then disconnect and reconnect it.


5. **Adjust Mounting Options**:

   Depending on how you mount the USB device, you can also set the permissions and ownership at the mounting stage. For example, you can modify your `/etc/fstab` file to specify the `umask`, `uid`, and `gid` options for the device. Here's an example entry in `/etc/fstab`:


   ```

   UUID=your_device_UUID /mount/point ntfs-3g defaults,uid=1000,gid=1000,umask=0022 0 0

   ```


   In this example, replace `your_device_UUID` with the actual UUID of the USB device, `/mount/point` with the desired mount point, and `uid` and `gid` with the user and group IDs you want to assign to the mounted filesystem. The `umask` value specifies the permissions mask.


6. **Remount the USB Device**:

   After making changes to `/etc/fstab`, you can remount the USB device using the `mount` command:


   ```bash

   sudo mount -a

   ```


These steps should help you change the default permissions for USB devices' filesystems on your Linux system. Be careful when modifying udev rules and `/etc/fstab`, as incorrect settings can cause issues.

Comments

Post a Comment

Popular posts from this blog

bad character U+002D '-' in my helm template

 In Helm templates, the hyphen character (`-`) can sometimes be treated as a reserved character, particularly when defining values or labels. To include a hyphen character in a Helm template without issues, you can use one of the following approaches: 1. **Quoting the Hyphen:**    You can enclose the hyphen in double quotes, like this:    ```yaml    key: "-"    ```    This way, Helm will interpret the hyphen as a string rather than an operator. 2. **Using Backticks:**    If you need to use the hyphen within a Go template function or inside backticks, you can escape it with a backslash (`\`), like this:    ```yaml    value: `{{ .Values.someField | printf "%s \\-" }}`    ```    The backslash prevents Helm from interpreting the hyphen as a special character. 3. **Variable Assignment:**    Assign the value to a variable and use it. For example:    ```yaml    {{- $hyphen := "-" }}    key: {{ $hyphen }}    ```    This way, you can use the variable `$hyphen` wher
Read more

GitLab pipeline stopped working with invalid yaml error

 When your GitLab pipeline has stopped working with an "invalid YAML" error, it means there's a problem with your `.gitlab-ci.yml` file. This could be due to syntax errors, incorrect indentation, or other issues in your pipeline configuration. Here's how to troubleshoot and resolve this issue: 1. **Check for Syntax Errors**:    Carefully review your `.gitlab-ci.yml` file for any syntax errors. Common issues include missing colons, indentation problems, or mismatched quotation marks. Use a YAML linter or an online YAML validator to identify and correct syntax errors. 2. **Indentation**:    YAML relies heavily on proper indentation. Make sure that all lines within the same block have consistent indentation (typically using spaces, not tabs). Incorrect indentation can cause YAML parsing errors. 3. **Dashes and Lists**:    Ensure that you use the correct syntax for lists (arrays) in YAML by starting each item with a dash (`-`). Be consistent with your use of dashes throug
Read more

How do I add a printer in OpenSUSE which is being shared by a CUPS print server?

 To add a printer in openSUSE that is being shared by a CUPS print server, you can use the following steps: 1. **Ensure CUPS Client is Installed:**    Make sure your openSUSE system has the CUPS client tools installed. You can install them using the following command:    ```bash    sudo zypper install cups-client    ``` 2. **Discover Available Printers:**    Use the `lpinfo` command to discover available printers on your CUPS print server. Replace `cups-server-hostname` with the hostname or IP address of your CUPS server:    ```bash    lpinfo -v -h cups-server-hostname:631    ```    This command should list the printers shared by the CUPS server. 3. **Add a Printer:**    Use the `lpadmin` command to add a printer. Replace `printer-name` with the name of the printer you want to add and `printer-uri` with the URI obtained from the `lpinfo` command:    ```bash    sudo lpadmin -p printer-name -E -v printer-uri    ```    For example:    ```bash    sudo lpadmin -p MyPrinter -E -v socket://cu
Read more