Tiny Core Linux
Tiny Core Extensions => TCE Talk => Extension requests => Topic started by: sm8ps on May 26, 2021, 11:53:16 AM
-
piCore version 13.0.3
Linux box 5.10.16-piCore #1 Wed Feb 17 04:05:50 UTC 2021 armv6l GNU/Linux
https://savannah.nongnu.org/projects/davfs2
I have tried to install compiletc.tcz but it does not find pc.tcz and I could not open a new thread about it because of a server error. Hopefully this try does go through!
-
I have tried to install compiletc.tcz but it does not find pc.tcz and I could not open a new thread about it because of a server error. Hopefully this try does go through!
pc.tcz? Never heard such extension :( In is not on compiletc.tcz dependency tree
-
Hi sm8ps
Thank you for reporting this. It's a typo in the gcc.tcz.dep file. It should have said mpc.tcz. I'll go fix it.
-
Hi bmarkus
Only armv6 was affected by this. The gcc.tcz.dep file has been updated. So have the .tree files.
-
Thanks for correcting the typo. I guessed it could be that but don't not have enough experience with compiling. tools.
I have been trying to reply but always hit a server error. It is almost impossible to communicate.
-
davfs2 posted - note that it was compiled on piCore-12.x and that I do not have access to a webdav share to test
-
Thanks, juanito for your support! After some fiddling, the extension does work well on piCore-13.0.3.
Three things need to be done and could be added to it in order to make it work according to its standard configuration file:
- fuse or fuse3 is a necessary dependency
- The user davfs2 should exist: adduser -SH davfs2
- The group davfs2 should exist: addgroup -S davfs2
After that, WebDAV-shares can be mounted. It seems that it does not recognize personalized secrets-files under /root/.davfs2 or ~tc/.davfs2. The only way I could get it to respect a secrets file was over-writing the system-wide /usr/local/etc/davfs2/secrets (which has to be included in .filetool.st.
Ctrl-A + Ctrl-C + Post (:
-
fuse3 added to dep file and info file adjusted
-
I double-checked the info file and it looks good. Thanks a lot for your efforts!
-
If you use “mount -t davfs2 …” do you still need to create the davfs2 user/group?
-
Yes, indeed! The mounting fails if the user or group does not exist. So the info file should read "user/group dsvfs2 need to exist" but I think one will figure that out. Otherwise the user and group could be created by some installation script.