Thus said Chad Perrin on Sat, 10 Aug 2013 20:21:46 -0600: > Why is naming them all foo.fossil important? Is that a hardcoded > extension expectation in the Fossil SCM sources that ensure the server > command will recognize the files -- and is it the only such extension > option for this purpose?
Yes, that's it. It only looks for fossils that end in a particular extension. This also means you cant't use the name of the file on the clone: fossil clone ssh://user@remote/project localproject.fossil vs fossil clone http://user@remote/project.fossil local > > * If you run the "fossil server" command as root, and if the > > directory containing repository files (and the repo files too) are > > owned by some non-root user, then Fossil will fork a copy of itself > > for each inbound request and put itself into a chroot jail as the > > user who owns the directory, before reading anything off of the > > wire. > > I read this as saying that the incoming requests will then only > interact with chrooted forks that are owned by an unprivileged user > account on the system. Is that correct? Is there any reason to expect > things may not work as expected on FreeBSD (considering I suspect most > of the devs use Linux-based systems)? Yes, I believe your description matches Dr. Hipp's description. If you run fossil in an unprivileged jailed account that already is chrooted, there is no need to run fossil as root unless you desire the functionality that fossil+root+chroot provides over what it does when it finds itself already in a chroot. One nice thing about having it run as root is that it will chroot to the owner of the directory which in some environments might make it easy to provide multiple user hosted repositories. I have never run it as root (I chroot prior to running fossil), but it should work just fine on FreeBSD. I use OpenBSD and haven't noticed any problems (aside from some fossil+SSH+Shell problems), and I don't see why running it on FreeBSD will present any problems. > Does it do all that without any additional configuration of Fossil > itself, the specific repository, or the host system? I belive so, yes, but only if you run it as root (obviously because only root can chroot) and you meet the criteria mentioned above. Andy -- TAI64 timestamp: 4000000052070130 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
