Re: Wine-fbsd64 updated to 1.3.31 (32bit Wine for 64bit FreeBSD)
2011/10/25 David Naylor naylor.b.da...@gmail.com: Hi, Hi, Packages [1] for wine-fbsd64-1.3.31 have been uploaded to mediafire [2] and the wine-fbsd64.diff patch has been updated. There is a known UDP related problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for details). To date there has been 1217 (+70) downloads from mediafire. The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. $ sudo pkg_add Downloads/wine-fbsd64-1.3.31,1.txz tar: /usr/local/share/wine/patch-nvidia.sh: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. A NVIDIA GRAPHICS DRIVER HAS BEEN DETECTED ON THIS SYSTEM AND THE AUTOMATED PATCHING HAS FAILED, execute (as root) sh /usr/local/share/wine/patch-nvidia.sh to get 2D/3D acceleration to work with the nvidia driver. Without this wine will crash when a program requires 2D/3D graphics acceleration. [...] $ file /usr/local/share/wine/patch-nvidia.sh /usr/local/share/wine/patch-nvidia.sh: cannot open `/usr/local/share/wine/patch-nvidia.sh' (No such file or directory) $ tar tf Downloads/wine-fbsd64-1.3.31,1.txz | grep -C 2 nvidia bin32/wmc bin32/wrc usr/local/share/wine/patch-nvidia.sh share/wine/fonts/coue1255.fon share/wine/fonts/coue1256.fon The problem here seems to be the trailing usr/local/ for patch-nvidia.sh file, which get actually installed into $PREFIX/usr/local/share/wine instead of $PREFIX/share/wine Regards, Romain PD: I used the fbsd9 package. md5 is ok. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
bsdtar --gname switch
Hi, According to bsdtar(1) manpage, tar has a --gname switch that permits to set an arbitrary groupname in the tar archive, but: $ tar -cf test.tar --gname root test.sh tar: Option --gname is not supported Usage: List:tar -tf archive-filename Extract: tar -xf archive-filename Create: tar -cf archive-filename [filenames...] Help:tar --help I get the same error for --uname and --gid switches. I'm running 9.0-BETA3 (r226421). Did those switches used to work in previous releases of FreeBSD ? Regards, Romain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Port dependencies
2011/4/3 Chris Telting christopher...@telting.org: seriously, this is why i want that debian+freebsd that was discussed recently. the kernel is ours and number one in the world. and the ports stuff is basically packages that more/less just-work. you can get the src =with= the pkg. How does debian get around all the make config options that we deal with? Such as does such and such package pull in samba... Or does debian just compile with every option more or less enabled? Debian GNU/kFreeBSD is a port that consists of GNU userland using the GNU C library on top of FreeBSD's kernel, coupled with the regular Debian package set. from http://www.debian.org/ports/kfreebsd-gnu/ So it seems they basically use their own packages and not the ports. Romain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
automating network configuration
Hello, I am looking for a way to automate the configuration of my network depending on its topology (don't know if it's the good word) : I would like to check the wired interface to see if a cable is plugged in (by looking at carrier status), if so, bring up the wired interface, if no bring up the wireless interface. Is there a way to do this? I was wondering if it is possible to do so by scripting rc.conf? Thanks in advance for any advice, Romain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Loader, MBR and the boot process
2010/1/22, Dan Naumov dan.nau...@gmail.com: Putting the swap into it's own slice and then putting FreeBSD into it's own slice worked fine. So why the hell can't they both coexist in 1 slice if the swap comes first? Similar problem here: I have a full-zfs system in a bsd slice, but I have the zfs-freebsd partition before the swap one. The problem is that the system doesn't seem to detect the swap partition partition (I see swapon: /dev/ada0s1b: No such file or directory during boot) % bsdlabel /dev/ada0s1 # /dev/ada0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 530432000 ZFS b: 9883342 53043200 swap c: 629265420unused0 0 # raw part, don't edit but to see ada0s1b in /dev/ I have to reload geom_bsd module (loading it at boot time doesn't work). Even though (but this seems to be another problem): % sudo swapon /dev/ada0s1b swapon: /dev/ada0s1b: Operation not permitted Regards, Romain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
