Easy iso mount?

[operadude]

Sorry, my fault, it's "isomount", it also has the counterpart isoumount. You need to use sudo, for isomount you give the ISO file name as argument, for the isoumount you just run it without arguments and it umounts any ISO you might have mounted.

Tried both "isomount" and "isoumount", which worked perfectly fine.

Just 2 questions:

1. I'm assuming that there's nothing wrong with the following when I run "isoumount" (unmounting) without "sudo": looks like "df" is trying to run, but apparently can't (without "sudo")?

Code: Select all

$ isoumount
df: /run/user/1000/doc: Operation not permitted
isoumount: Unmounted /mnt/iso/iso2

2. Is this a normal situation after unmounting?

Code: Select all

tmpfs on /mnt/iso type tmpfs (rw,relatime,size=1024k,inode64)

Sounds/Looks like what @BitJam said earlier:

The /mnt/iso/ directory is mounted as tmpfs so all of its subdirectories should disappear automatically when the system shuts down.

Here's a closer look at what remains in my "/mnt/iso" directory after using "isoumount".

Code: Select all

opera-dude@GA-H270-HD3:/mnt/iso
$ ls -al
total 4
drwxrwxrwt  2 root root   40 Oct 30 13:35 .
drwxr-xr-x 15 root root 4096 Oct 30 13:34 ..

All in all, looks good!

Anybody...Just let me know if anything looks wrong!

[Adrian]

You need to run it with sudo. Also listen to BitJam since he wrote the nice tool :)

[operadude]

You need to run it with sudo. Also listen to BitJam since he wrote the nice tool :)

Thanks.

When I ran it with "sudo", there was no error report.

Yeah, and according to @BitJam , when running the unmount feature (isoumount), it cleaned-up the tmpfs on /mnt/iso.

We're in business!

[m_pav]

Code: Select all

man isomount

produces the manual information, which tells me that it's already installed on my system.

@operadude
Just a FYI, the appropriate commands to see if a package is installed or available are;

Code: Select all

$ which isomount
/usr/local/bin/isomount

The which command returns the path of the package name if found, or returns to the terminal prompt without producing anything if the package is not found.

Code: Select all

$ apt policy isomount
isomount:
  Installed: 0.1.5mx19+1
  Candidate: 0.1.5mx19+1
  Version table:
 *** 0.1.5mx19+1 500
        500 http://la.mxrepo.com/mx/repo bookworm/main amd64 Packages
        500 http://la.mxrepo.com/mx/repo bookworm/main i386 Packages
        100 /var/lib/dpkg/status

The apt policy command produces the information contained about the package from the apt database, including the version number if installed, or (none) if it's not installed.

[Adrian]

Frankly, I'm not a fan of /usr/local/bin location for this binary... binaries from packages that come from repo should probably be in the more standard /usr/bin/ location

[operadude]

Code: Select all

man isomount

produces the manual information, which tells me that it's already installed on my system.

@operadude
Just a FYI, the appropriate commands to see if a package is installed or available are;

Code: Select all

$ which isomount
/usr/local/bin/isomount

The which command returns the path of the package name if found, or returns to the terminal prompt without producing anything if the package is not found.

Code: Select all

$ apt policy isomount
isomount:
  Installed: 0.1.5mx19+1
  Candidate: 0.1.5mx19+1
  Version table:
 *** 0.1.5mx19+1 500
        500 http://la.mxrepo.com/mx/repo bookworm/main amd64 Packages
        500 http://la.mxrepo.com/mx/repo bookworm/main i386 Packages
        100 /var/lib/dpkg/status

The apt policy command produces the information contained about the package from the apt database, including the version number if installed, or (none) if it's not installed.

@m_pav :

Thanks for the reminders!

I do know about "which" and "apt policy", but I was just looking for some info on "isomount", and assumed it was installed, so went with "man" in this case.

I always welcome Best Practices

[operadude]

Frankly, I'm not a fan of /usr/local/bin location for this binary... binaries from packages that come from repo should probably be in the more standard /usr/bin/ location

Is there any way for the little guy, like me, to do something about this, or is this an issue for the developers and/or packagers/maintainers?

Just curious....

[Adrian]

This is not an issue that need to worry about, it's like "I like color yellow, developer used green"

[operadude]

@Adrian :

Very well, then.

I shall continue with my very important Halloween activities

Apropos:



Sorry, couldn't resist!

Only time of year I would every use these emojis!