userlandfs does not work correctly if installed in home (instead of system)
|Reported by:||ttcoder||Owned by:||bonefish|
|Has a Patch:||no||Platform:||All|
While testing further I ended up with userland-fs installed in home/config/packages (instead of system/packages), and things don't work as expected. Symptoms:
/dev/disk/atapi/3/master/0device shows up as soon as the audio CD is inserted (not waiting for a mount command to be issued), and even with auto-mounting disabled in Tracker preferences; one can see it pop up in real time by leaving DriveSetup open when inserting the CD.
- when the actual mount command is issued in Terminal, it returns "mount: No such file or directory":
Executing userlandfs line <mkdir -p /audiocd ; mount -t userlandfs -p cdda /dev/disk/atapi/3/master/raw /audiocd> mount: No such file or directory
Took me a while to understand the problem was due to the package being in home, because that status_t (no such file) is the same one returned when you mistype the filesystem name and invoke e.g. -t userlandfs -p cddda.
- improve error handling, to distinguish those 2 error cases
- look into why userlandfs wants to be installed in system
- or if it's the case that some packages simply cannot live in home at all, extend the hpkg properties/syntax of dependancies to manage this ; use-case: I have declared a
depends: userland-fsdependancy in my CD-ripping app, which means if that application package is installed in system then userlandfs is correctly installed in system, but if the application is installed in home then userlandfs is downloaded and installed in home too.
Change History (7)
comment:3 by , 5 years ago
|Summary:||userland/cdda does not work correctly if installed in home (instead of system) → userlandfs does not work correctly if installed in home (instead of system)|