Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.3 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.3,1.tbz) = 0592e0b1226314a7061ef5745fa0e59f MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.3,1.txz) = 002e343a7bcb0cea7456422b75aec8f6 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh [*] To install the port first fix the arch tag use the 'fix-arch.sh' script from mediafire [2] signature.asc Description: This is a digitally signed message part.
Re: HOWTO: FreeBSD ZFS Madness (Boot Environments)
Good to see you've finally been burned.
You'll never make that mistake again. :)
I liked that syntax:
ASD {
asd
} || {
bsd
}
mostly because of syntax highlighting, to be precise highlighting
of the second bracket of a pair at editors, nor VIM neither GEANY
highlight if/then/elif/else/fi unfortunately, seems that I will have
to live with that ;p
OK, I'll give that a try. Thanks for being persistent with me.
Did it worked?
Regards,
vermaden
--
...
___
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: HOWTO: FreeBSD ZFS Madness (Boot Environments)
vermaden == vermaden verma...@interia.pl writes:
Good to see you've finally been burned.
You'll never make that mistake again. :)
vermaden I liked that syntax:
vermaden ASD {
vermaden asd
vermaden } || {
vermaden bsd
vermaden }
vermaden mostly because of syntax highlighting, to be precise highlighting
vermaden of the second bracket of a pair at editors, nor VIM neither GEANY
vermaden highlight if/then/elif/else/fi unfortunately, seems that I will have
vermaden to live with that ;p
Emacs indents it nicely, and colorizes the keywords so that it stands out.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
___
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
does anyone care about periodic scripts?
Hi all. It seems that patches to periodic scripts have hard time coming into the tree. I personally filed http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/165817 and still there's no move despite change is purely cosmetical and just fixes right way of things. And this is not just one and only case, pr's are numerous and get minimal to no attention at all: http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/165956 http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/30938 How can I assist with this pr's? Whom should I bug to get some answer about them? -- Sphinx of black quartz judge my vow. ___ 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: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)
--- Оригінальне повідомлення --- Від кого: David Naylor naylor.b.da...@gmail.com Кому: freebsd-emulat...@freebsd.org, freebsd-questions@freebsd.org Дата: 7 травня 2012, 11:45:18 Тема: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD) Hi, Packages [1] for wine-fbsd64-1.5.3 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng* [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.3,1.tbz) = 0592e0b1226314a7061ef5745fa0e59f MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.3,1.txz) = 002e343a7bcb0cea7456422b75aec8f6 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17 [2] http://www.mediafire.com/wine_fbsd64[3] http://wiki.freebsd.org/pkgng[4] The patch is located at /usr/local/share/wine/patch-nvidia.sh [*] To install the port first fix the arch tag use the 'fix-arch.sh' script from mediafire [2] root@nonamehost# pkg_add wine-fbsd64-1.5.3,1.txz tar: +CONTENTS: Not found in archive tar: Error exit delayed from previous errors. pkg_add: tar extract of /home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz failed! pkg_add: unable to extract table of contents file from '/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz' - not a package? md5 wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz MD5 (wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17 ___ 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: Building kernel outside of /usr/src (with an unprivileged user)
On 1 May 2012 13:02, Matthias Petermann matth...@d2ux.net wrote: Hello, while trying to build a patched CURRENT src on a STABLE FreeBSD 9 I was wondering if it would be possible to have the source directory (src) in a different place from /usr (e.g. in /home/myuser/src) where it can be built with an unprivileged user and without interference with the STABLE sources in /usr/src. Does anyone have an idea how to achieve this? buildkernel and buildworld function without superuser permission. Just check out the directory in a different and run the typical commands. -- Eitan Adler ___ 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: help debug bwn(4) wireless
In freebsd-questions Digest, Vol 414, Issue 1, Message: 13 On Sun, 06 May 2012 21:48:19 +0100 Chris Whitehouse cwhi...@onetel.com wrote: On 06/05/2012 17:31, Ian Smith wrote: Anton, I'm not sure what the state of the art is for multiple network profiles for such as wireless vs wired, home and work etc, but look around. I recall one called just 'profile' from years ago, and more recently talk of 'failover' setups for wired/wireless nets (probably in n...@freebsd.org), but I've no time for hunting tonight. Anyone? Would that be lagg? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html It would indeed, thanks Chris. Example 32-3. Failover Mode Between Wired and Wireless Interfaces might almost meet Anton's requirements? cheers, Ian ___ 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
Write only directory.
Is it possible to let a user write to a directory but not access the file after they write it? The file is being transferred via scp and after the transfer I don't want them to be able to re-fetch or even get a directory listing. Thanks. -- Paul Halliday http://www.squertproject.org/ ___ 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: Write only directory.
Paul == Paul Halliday paul.halli...@gmail.com writes: Paul Is it possible to let a user write to a directory but not access the Paul file after they write it? Paul The file is being transferred via scp and after the transfer I don't Paul want them to be able to re-fetch or even get a directory listing. scp is via ssh. with ssh, they get a complete command line. how are you going to prevent *that*? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion ___ 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: Write only directory.
On Mon, May 7, 2012 at 3:49 PM, Randal L. Schwartz mer...@stonehenge.com wrote: Paul == Paul Halliday paul.halli...@gmail.com writes: Paul Is it possible to let a user write to a directory but not access the Paul file after they write it? Paul The file is being transferred via scp and after the transfer I don't Paul want them to be able to re-fetch or even get a directory listing. scp is via ssh. with ssh, they get a complete command line. how are you going to prevent *that*? The users shell is /bin/false and sshd is setup like: Match User a_user ChrootDirectory %h ForceCommand internal-sftp AllowTcpForwarding no ___ 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: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)
On Monday, 7 May 2012 18:09:29 fidaj wrote: --- Оригінальне повідомлення --- Від кого: David Naylor naylor.b.da...@gmail.com Кому: freebsd-emulat...@freebsd.org, freebsd-questions@freebsd.org Дата: 7 травня 2012, 11:45:18 Тема: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD) root@nonamehost# pkg_add wine-fbsd64-1.5.3,1.txz tar: +CONTENTS: Not found in archive tar: Error exit delayed from previous errors. pkg_add: tar extract of /home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz failed! pkg_add: unable to extract table of contents file from '/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz' - not a package? md5 wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz MD5 (wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17 To install wine-fbsd64 on FreeBSD 10 please do: # make -C /usr/ports/ports-mgmt/pkg install clean # sh fix-arch.sh wine-fbsd64-1.5.3,1.txz # pkg add wine-fbsd64-1.5.3,1.txz fix-arch.sh is available from mediafire. Regards signature.asc Description: This is a digitally signed message part.
Re: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)
В Mon, 7 May 2012 21:04:46 +0200 David Naylor naylor.b.da...@gmail.com пишет: On Monday, 7 May 2012 18:09:29 fidaj wrote: --- Оригінальне повідомлення --- Від кого: David Naylor naylor.b.da...@gmail.com Кому: freebsd-emulat...@freebsd.org, freebsd-questions@freebsd.org Дата: 7 травня 2012, 11:45:18 Тема: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD) root@nonamehost# pkg_add wine-fbsd64-1.5.3,1.txz tar: +CONTENTS: Not found in archive tar: Error exit delayed from previous errors. pkg_add: tar extract of /home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz failed! pkg_add: unable to extract table of contents file from '/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz' - not a package? md5 wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz MD5 (wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17 To install wine-fbsd64 on FreeBSD 10 please do: # make -C /usr/ports/ports-mgmt/pkg install clean # sh fix-arch.sh wine-fbsd64-1.5.3,1.txz # pkg add wine-fbsd64-1.5.3,1.txz fix-arch.sh is available from mediafire. Regards Thanks! ___ 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: kernel configuration file
Bernt Hansson b...@bananmonarki.se wrote: 2012-05-06 20:23, Robert Bonomi skrev: Including *every* loadable module, whether or not you actually use it. That's not really true, at least not for me, and I have not made any changes to the build environment. The loadable module that I actually use is bktr.ko, that one among others does not get built. I'd guess that bktr.ko is a 'third-party' module, found in a port, and not part of the base system. I found that every loadable kernel module in the base system is, or at least was, rebuilt. I haven't used make buildkernel in several years -- I use a 'monolithic' kernel, with everything compiled in, and loadable modules disabled. That way I always know _exactly_ what cabilities exist, and what security holes I _don't_ have to worry about. ___ 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: Write only directory.
Paul Halliday paul.halli...@gmail.com writes: On Mon, May 7, 2012 at 3:49 PM, Randal L. Schwartz mer...@stonehenge.com wrote: Paul == Paul Halliday paul.halli...@gmail.com writes: Paul Is it possible to let a user write to a directory but not access the Paul file after they write it? Paul The file is being transferred via scp and after the transfer I don't Paul want them to be able to re-fetch or even get a directory listing. scp is via ssh. with ssh, they get a complete command line. how are you going to prevent *that*? The users shell is /bin/false and sshd is setup like: Match User a_user ChrootDirectory %h ForceCommand internal-sftp AllowTcpForwarding no There is also shells/scponly for this kind of thing. As for the file permissions question: not sure how to tackle that. -- - Frank ___ 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: Write only directory.
On 07/05/2012 20:38, Paul Halliday wrote: Is it possible to let a user write to a directory but not access the file after they write it? The file is being transferred via scp and after the transfer I don't want them to be able to re-fetch or even get a directory listing. Hi, If user has no shell access I suppose the problem is that the user might be able to overwrite an existing file. The problem is what owner/permissions/flags the files will have after transfer. I don't know if this will work, but check if setting append only flag on a directory might do. I would expect the append only flag on a directory to allow only creating new files, so existing files cannot be overwritten. Other flags might also be required, also check what you can do with ACL and extended attributes. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ 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: Write only directory.
On May 7, 2012, at 11:38 AM, Paul Halliday wrote: Is it possible to let a user write to a directory but not access the file after they write it? The file is being transferred via scp and after the transfer I don't want them to be able to re-fetch or even get a directory listing. A directory with 0300 / 0330 umask permissions will prevent directory listing, but if they know the filename, they can still read from it as a necessary consequence of being able to write to it (think of appending data). It sounds like you are trying to implement the SFTP equivalent of an FTP incoming upload dropbox, so the comments in man ftpd might be helpful. However, it might be easier to setup a cronjob every minute which moves any files in the dropbox location to some other place for review and processing, which will prevent read access as well as making directory listings moot. (People offering anonymous FTP incoming tend to do this, even if their ftpd offers support for blocking read access for anonymous users, etc...) Regards, -- -Chuck ___ 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: help debug bwn(4) wireless
On Tue, May 08, 2012 at 03:07:04AM +1000, Ian Smith wrote: In freebsd-questions Digest, Vol 414, Issue 1, Message: 13 On Sun, 06 May 2012 21:48:19 +0100 Chris Whitehouse cwhi...@onetel.com wrote: On 06/05/2012 17:31, Ian Smith wrote: Anton, I'm not sure what the state of the art is for multiple network profiles for such as wireless vs wired, home and work etc, but look around. I recall one called just 'profile' from years ago, and more recently talk of 'failover' setups for wired/wireless nets (probably in n...@freebsd.org), but I've no time for hunting tonight. Anyone? Would that be lagg? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html It would indeed, thanks Chris. Example 32-3. Failover Mode Between Wired and Wireless Interfaces might almost meet Anton's requirements? Thanks for all your recommendations, guys. I'll get reading. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: kernel configuration file
On Mon, 7 May 2012 15:01:31 -0500 (CDT), Robert Bonomi wrote: Bernt Hansson b...@bananmonarki.se wrote: 2012-05-06 20:23, Robert Bonomi skrev: Including *every* loadable module, whether or not you actually use it. That's not really true, at least not for me, and I have not made any changes to the build environment. The loadable module that I actually use is bktr.ko, that one among others does not get built. I'd guess that bktr.ko is a 'third-party' module, found in a port, and not part of the base system. No, it's part of the base system. I've been using bktr _in_ kernel for many years (FreeBSD 5 and 7), but since 8.0, it does not build anymore. However, the module _does_ correctly build. The documentation is in man 4 bktr. A typical use (with the PAL option, because I don't have Never The Same Color here), did work in the past like this: device bktr options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_PAL options BKTR_USE_PLL options BKTR_GPIO_ACCESS options BKTR_USE_FREEBSD_SMBUS Today, I need to use /boot/loader.conf with those entry bktr_load=YES Works for my Haupauge WinTV PCI video + tuner card, even the options (PAL) seem to magically work! :-) I found that every loadable kernel module in the base system is, or at least was, rebuilt. That's correct so far. Additionally, all components specified by the kernel configuration file will be rebuilt, which in case of _no_ alteration is the content of GENERIC. As I said, there may be parts that one can safely drop (e. g. WLAN, floppy, ISDN or sound for a server). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: HOWTO: FreeBSD ZFS Madness (Boot Environments)
Emacs indents it nicely, and colorizes the
keywords so that it stands out.
Indentification is not a problem, it work both
in geany and vim.
Probably I haven't made clear what I meant ;)
Take a look at this picture:
http://ompldr.org/vZG50bQ
The brackets in that specific section (asd) are
highlighted, other are not, its not possible with
if/then/fi, only the keywords are highlighted,
but they are highlighted for the whole script so ... ;)
With { } I can also (un)fold the section/function,
its not possible with if/then/fi.
Regards,
vermaden
--
...
___
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
Wterm and FreeBSD 9
Greetings...
For FreeBSD 8, we see this for wterm:
BROKEN= does not compile
.if ${OSVERSION} 97
BROKEN= fails to build with new utmpx
.endif
I'd like to confirm that wterm will build and run on 9. I'm currently
running 8.3-RELEASE-p1 FreeBSD 8.3-RELEASE-p1 #0.
Does anyone know?
Thanks, and best regards,
Joe
___
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: Wterm and FreeBSD 9
On 7 May 2012 19:35, Joe Altman freebsd-annou...@chthonic.com wrote:
Greetings...
For FreeBSD 8, we see this for wterm:
BROKEN= does not compile
.if ${OSVERSION} 97
BROKEN= fails to build with new utmpx
.endif
I'd like to confirm that wterm will build and run on 9. I'm currently
running 8.3-RELEASE-p1 FreeBSD 8.3-RELEASE-p1 #0.
Does anyone know?
Dunno, it wants WMaker.h, which they aren't shipping any more.
Looks like wterm may be obsolete.
--
--
___
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
