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 patc
> 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/
> "vermaden" == vermaden 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 pre
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 o
--- Оригінальне повідомлення ---
Від кого: "David Naylor"
Кому: 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 mediaf
On 1 May 2012 13:02, Matthias Petermann 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 unp
In freebsd-questions Digest, Vol 414, Issue 1, Message: 13
On Sun, 06 May 2012 21:48:19 +0100 Chris Whitehouse 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,
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/
__
> "Paul" == Paul Halliday 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
On Mon, May 7, 2012 at 3:49 PM, Randal L. Schwartz
wrote:
>> "Paul" == Paul Halliday 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>
On Monday, 7 May 2012 18:09:29 fidaj wrote:
> --- Оригінальне повідомлення ---
> Від кого: "David Naylor"
> Кому: 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# pk
В Mon, 7 May 2012 21:04:46 +0200
David Naylor пишет:
> On Monday, 7 May 2012 18:09:29 fidaj wrote:
> > --- Оригінальне повідомлення ---
> > Від кого: "David Naylor"
> > Кому: freebsd-emulat...@freebsd.org, freebsd-questions@freebsd.org
> > Дата: 7 травня 2012, 11:45:18
> > Тема: Wine-fbsd64 upda
Bernt Hansson 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
Paul Halliday writes:
> On Mon, May 7, 2012 at 3:49 PM, Randal L. Schwartz
> wrote:
>>> "Paul" == Paul Halliday 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 a
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 sh
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 direc
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
> wrote:
> > On 06/05/2012 17:31, Ian Smith wrote:
> > > Anton, I'm not sure what the state of the art is for multiple ne
On Mon, 7 May 2012 15:01:31 -0500 (CDT), Robert Bonomi wrote:
>
> Bernt Hansson 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
> > chang
> 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
hi
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
On 7 May 2012 19:35, Joe Altman 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
> ru
21 matches
Mail list logo
