Re: Port dependency tool (if that's what you'd call it)
Modulok wrote: I'm not quite sure how to put into word what I want, so bear with me. Is there a tool in the base system which does something along these lines: 1. Look at the makefile of a given port as far as its RUN_DEPENDS and BUILD_DEPENDS. 2. Subtracting what I have already installed, provide me with information about what would be fetched (and possibly installed) in an easy-to-digest format, recursively (for all dependents of dependents ... and so on). If not part of the base system, is there a port which offers this functionality? The standard ports for this kind of functionality are port-mgmt/portupgrade port-mgmt/portmaster 'portupgrade' is the older utility; 'portmaster' has recently come on the "scene", with slightly different aims. I use 'portupgrade' as I haven't really spent the time to learn about 'portmaster'. Once 'portupgrade' is installed, and you have built its database with 'pkgdb', you should be able to answer your second question via freebsd$ portupgrade --noexecute --upward-recursive PORTNAME where PORTNAME is the name of the port (qv. 'ports_glob' for how this is specified) to give you information on what needs to be updated. You might need to trim the output a bit to get the succinct list of dependencies that need updating, but the output of 'portupgrade' is quite regular so a little regexp'in in your preferred scripting language should bring you to the result you want. There may be other more direct routes to the information you seek, but this way will definitely work. -- <[EMAIL PROTECTED]> "[T]his is not a disentanglement from, but a progressive knotting into." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysutils/fusefs-wdfs [was Re: How to mount WebDAV in FreeBSD?]
[Following up my own post] I would like to mount an SSL enabled WebDAV filesystem with FreeBSD as a filesystem. I can successfully mount WebDAV/ssl with gnomevfs2 using the nautilus2 GUI, but then the filesystem does not seem to be accessible as a mounted filesytem that is known to the BSD kernel (i.e. it doesn't show up via df(1)). There was the start of a project [[1]] to mount gnomevfs URIs under Linux, but is seems to have died. Maybe I could crib the code if someone has a copy? > [[1]] http://primates.ximian.com/~sandino/gnomevfs-mount > I could not find any information on where this code went: it seems to be lost, although various Linux binaries RPMs seem to be floating around. The developers of gnomevfs2 are currently thinking of overhauling their entire architecture, so maybe this would not be such a smart development path to run down at this point The other option seems to be 'sysutils/fusefs-wdfs' but it seems to be very unstable. Actually, I retract this comment. If one actually mounts the WebDAV filesytem as an unprivileged user, wdfs seems quite stable. My problems seem to arise when I performed the mount as root, which when the wdfs process dies, would crash the machine. NB: in order to use wdfs as an unprivileged user, one must not only set the sysctl vfs.usermount to 1, one also has to change devfs to make the newly created /dev/fuse[0-9]+ devices be world read/writable unix# defvs add path fuse\* mode 666 Maybe this should be added to the port pkg-message (if my understanding is correct)? -- <[EMAIL PROTECTED]> "[T]his is not a disentanglement from, but a progressive knotting into." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to mount WebDAV in FreeBSD?
I would like to mount an SSL enabled WebDAV filesystem with FreeBSD as a filesystem. I can successfully mount WebDAV/ssl with gnomevfs2 using the nautilus2 GUI, but then the filesystem does not seem to be accessible as a mounted filesytem that is known to the BSD kernel (i.e. it doesn't show up via df(1)). There was the start of a project [[1]] to mount gnomevfs URIs under Linux, but is seems to have died. Maybe I could crib the code if someone has a copy? The other option seems to be 'sysutils/fusefs-wdfs' but it seems to be very unstable. Any ideas on what I could look at to solve this --- [[1]] http://primates.ximian.com/~sandino/gnomevfs-mount -- <[EMAIL PROTECTED]> "[T]his is not a disentanglement from, but a progressive knotting into." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: On 31/05/2006, at 11:30 PM, Steve Bertrand wrote: Take a look at the 'ServerName' directive in your httpd.conf file. Try uncommenting said directive, and put your IP address beside it. This line is already in place ServerName 127.0.0.1:80 I can confirm this behavior with www/apache22 for a FBD_6_1 machine not in DNS. My solution: I commented out the load of mod_unique_id in httpd.conf making everything work just fine. Looking at the documentation of mod_unique_id convinced me that I would only need it for some sort of server-side application that could not provide itself with a concept of a session. I haven't dug into the mod_unique_id code to find out what it is trying to resolve. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libgnome-keyring.so.0 not found
Jim Angstadt wrote: Hi All, Fortunately, after another multi-day "portmanager -u -l -y" run, I am able to get into X. Unfortunately, I cannot run gedit, gnome-terminal or nautilus. X provided 3 error messages which I have manually copied: /libexec/ld-elf.so.1: Shared object "libgnome-keyring.so.0" not found, required by "gedit" [...] Assuming that these libraries exist on the filesystem, you might try refreshing the dynamic library cache via: root# ldconfig -m /usr/X11R6/lib Over the last week, something in the portupgrade process changes the ownership of /usr/X11R6/lib to the user that invokes portupgrade with "-s", which breaks this step in the course of portupgrade (ldconfig refuses to run on directories not owned by its invoking user). I haven't been able to track down where this is occuring, but changing the ownership of /usr/X11R6/lib back to root and refreshing the cache fixes this sort of problem for me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"