Search results

FTR This was solved in 2016 in the context of using SAMBA protocol version SMBv1 instead of SMBv2 or SMBv3. Newer SAMBA versions (net/samba4xx) do understand versions 2 and 3, but FreeBSD's mount_smbfs does not. So today, the solution from May 2016 does not work anymore.

Just for the record: the port was updated today from 2.9.3 to 2.9.4 (by fjoe@, many thanks to him).

I made a PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=170194) on July, 26th. I don't know if Max (the maintainer) is already looking for it. In the meantime you could patch your port 2.9.3 towards 2.9.4 with help of this PR. It should work as expected. Hope this helps, Rainer

No, that is not my problem. I have a working, native jdk16 environment and want to hold it. I am not interested in openjdk at this time. In previous versions eclipse was able to build on jdk16. There must be a reason for changing this towards openjdk ...

Hmmm, I am afraid this is not the solution. At least for me it does not work. In java/eclipse/Makefile there is explicitly defined JAVA_VENDOR=openjdk So there must be a reason for it?

I am working with 9.0-CURRENT (amd64). I installed an i386 ready package of grub (legacy) and it works like a charm. >file /usr/local/sbin/grub /usr/local/sbin/grub: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 9.0 (900004)...

I think there is a misunderstanding between greenfrog and radical. The first tries to work with sysutils/grub2 and the second tells about his experiences with sysutils/grub. For me the older (legacy) version of grub works nice, the newer version 2 does not. There is at least one other thread...

If I do no misunderstand, you can use portupgrade in combination with /usr/local/etc/pkgtools.conf. In section HOLD_PKGS you can integrate that kind of ports. Hope this helps.

Did you study http://cran.r-project.org/web/packages/ and http://www.bioconductor.org/? There are thousands of special packages for R, some of them are 'pharmacological'. see several R mailinglists on http://www.r-project.org/mail.html, especially R-help for beginners.

As far as I can evaluate, /compat/linux/home/ was created from print/acroread8. Once it exists, it seems that googleearth uses it, too. I see this behaviour on three machines, all 9.0-CURRENT (amd64). Solution: Deleting /compat/linux/home/ seems to bring no disadvantages. Now acroread and...

I think the behaviour of googleearth installation changed in last update. I am no friend of additional symlinks, that had not automatically been installed from the port :-( The newest port seems to use only /compat/linux/home/USERNAME/.googleearth/ for the lockfile. As far as I can see...

No, this does not clear /compat/linux/home/USERNAME/.googleearth/instance-running-lock

On freebsd-ports@freebsd.org mailing list Janne Snabb turned out, that it seems this error only happens with perl threads enabled. Without enabling threads all works fine.

Hmm, in your quoted answers from sem it seems, the he was able to install and configure with grub2 and after that successfully reboot his system. I tried on three different systems (all amd64) and grub2 was barely able to detect any devices. Just the following works: #grub-probe -d...

From July 5th on there is a Grub2 version on FreeBSD (sysutils/grub2), thanks to sem. But I am afraid this port is not working correctly: no update-grub, grub-probe and grub-install did not find devices etc. I tried for some hours but had no luck to get it installing ;-( That is really...

You may have a look at http://pub.allbsd.org/FreeBSD-snapshots/.

Yes, it was reported some time ago. Build a grub package on i386 (before replace it with amd64) and later pkg_add this 32-bit package in amd64 system. It should work as it does for me. If I am not mistaken, you have to copy all files from /usr/local/share/grub/i386-freebsd/ to /boot/grub/...

We should mention that Thomas Zander is working on a newer port for this. So please read on the full thread, see http://docs.freebsd.org/cgi/getmsg.cgi?fetch=220190+0+current/freebsd-ports an following :-)

Ok, thanks for this clarification. Looking in http://en.wikipedia.org/wiki/X86-64 I found some more infos. One further question about this: so it is possible to run FreeBSD amd64 on for example Intel Core 2 Duo in full 64bit mode?

Am I right that your CPU is Intel Pentium D? I am irritated about 'K8-class' ... As far as I know amd64 mode is only available on AMD CPUs.