Robert Bonomi wrote:
> Somebody saying "I'll buy it, if it supports _this_ scanner"
> is motivation.
So perhaps what is needed is for N FreeBSD users to say "I'll buy
it, if it runs on FreeBSD." Any guesses on how large an N would
be needed to provide sufficient motivation?
Yep, that was it. Thanks very much Yuri.
On Sat, Feb 5, 2011 at 3:07 PM, Yuri Pankov wrote:
> On Sat, Feb 05, 2011 at 02:24:31PM +1000, Rob wrote:
> > Hi,
> >
> > I'm running FreeBSD 8.1-RELEASE (running on VMWare Server 2.0.2) and am
> > having some odd issues the formatting of man pages.
> >
>
On Sat, 05 Feb 2011 00:53:00 -0800
per...@pluto.rain.com wrote:
> So perhaps what is needed is for N FreeBSD users to say "I'll buy
> it, if it runs on FreeBSD." Any guesses on how large an N would
> be needed to provide sufficient motivation?
Heh...when I asked Ed about support for 64-bit versi
Em Sáb, 2011-02-05 às 00:53 -0800, per...@pluto.rain.com escreveu:
> Robert Bonomi wrote:
>
> > Somebody saying "I'll buy it, if it supports _this_ scanner"
> > is motivation.
>
> So perhaps what is needed is for N FreeBSD users to say "I'll buy
> it, if it runs on FreeBSD." Any guesses on how
Sergio de Almeida Lenzi writes:
> As FreeBSD comes out with a new version about a year (or two..)
> 7.x -> 8.x -> 9.x a version of the sofware needs to be done
> (compiled) seldom.
If the program is well-written, it may well be that
re-compiling is all that needs to be done.
(
On 2 February 2011 15:20, krad wrote:
> On 2 February 2011 12:18, Ivan Voras wrote:
>> On 02/02/2011 05:52, krad wrote:
>>>
>>> Hi All,
>>>
>>> A quick question. Im upgrading my filer at home to have 2x 2tb samsung
>>> F4EG drives. I believe these are 4k drives. I'm intending to use the
>>> gnop
I have a couple of entries in my /etc/mail/aliases that manipulate the contents
of an e-mail message. For example,
file: "| cat > /home/user/file.incoming"
receives an e-mail message and writes it to the hard drive. Another example:
format: "| sed 's/^.$/~~/g' | sed 's/^$/~~/g' |
Why would doing a printf(9) in a device driver (usb, firewire, probably
others) cause an obscenely long lockout on
/usr/src/sys/kern/uipc_sockbuf.c:148 (sx:so_rcv_sx) ?
Printf(9) alone isn't the problem, adding printfs to chown(2) does not
cause the problem, but printfs from device drivers do.
G
Hello,
After updating all ports on 8.1-RELEASE, nedit has a problem. The right
mouse button works ok in the toolbar but if it is pressed in the text
area, for example to copy a block of text, the cursor changes shape and
the X session becomes completely locked up. I have to stop X and
restart it
On 05/02/2011 21:22, dieter...@engineer.com wrote:
Why would doing a printf(9) in a device driver (usb, firewire, probably
others) cause an obscenely long lockout on
/usr/src/sys/kern/uipc_sockbuf.c:148 (sx:so_rcv_sx) ?
You should ask this question on freebsd-hackers@.
Printf(9) alone isn't
All,
I have a laptop running 8.2-prerelease GENERIC. I have virtualbox ose
3.2.12 from ports (and kmod as well).
I've only installed windows guests in vbox. I've installed windows 2008
server 64, windows vista 64bit, and windows 7 32bit. I have the vbox
hdd images on an NTFS filesystem mounted
On Sat, 05 Feb 2011 14:33:50 -0700, Fred Boatwright wrote:
> Hello,
>
> After updating all ports on 8.1-RELEASE, nedit has a problem. The right
> mouse button works ok in the toolbar but if it is pressed in the text
> area, for example to copy a block of text, the cursor changes shape and
> the X
Fred Boatwright wrote:
> After updating all ports on 8.1-RELEASE, nedit has a problem. The right
> mouse button works ok in the toolbar but if it is pressed in the text
> area, for example to copy a block of text, the cursor changes shape and
> the X session becomes completely locked up. I have
13 matches
Mail list logo