Re: Xorg 7.2 and FreeBSD 6.2-p5 VMWARE vmmouse problem

2008-01-09 Thread Sam Lawrance


On 09/01/2008, at 10:31 AM, Bob Finch wrote:


On 10/10/2007, at 17:00:22, Sam Lawrance wrote:

On 10/07/2007, at 11:53 AM, Webster, Andrew wrote:



Howdy,



I was successfully able to get Xorg upgraded to 7.2 by just
installing them from scratch as opposed to trying to upgrading an
existing system, BUT I’ve run into a problem…



While running VMWare Server 1.0.3 with FreeBSD 6.2-p5 and Xorg 7.2,
the mouse pointer behaves very oddly.

The pointer appears in the wrong place on the screen for where the
system actually thinks that it is.

I’m using the vmmouse driver part of the Xorg system, as the
regular mouse driver doesn’t appear to work at all, unless some
settings are amiss.

I really like the vmmouse drive because you can move the pointer in/
out of the window as you do with regular windows guest OSes.



Has anyone experienced similar problems and/ or know of a fix for
this?



Andrew,

I just set up VMWare Fusion with FreeBSD and have a problem that
might be related.  Ascii art time:
_
|_| |
|   |
|   |
|___|

The pointer appears normally on the screen.  However, clicking around
the screen does not work except in a small area in the top left
corner.  Moving the mouse within this tiny corner seems to scale up
and operate on the entire screen.  Eg. if I click and drag across the
tiny corner, I can see the selection appear across the entire  
desktop.


Is this similar to your issue?  Did you find a resolution?


Sam,

I ran into this problem on FreeBSD 7.0 RC1 with Xorg 7.3 using the
VMWare mouse driver (vmmouse).

Apparently, X server 1.4.0 in Xorg 7.3 no longer calls the  
conversion_proc

function in the mouse driver.  The VMWare mouse driver depends on that
call to scale the mouse coordiates to the screen size.

As a workaround, I fetched the x11-drivers/xf86-input-vmmouse port and
patched src/vmmouse.c by hand before installing it:

bob polaris[9]: diff -u orig/xf86-input-vmmouse-12.4.3/src/ 
vmmouse.c xf86-input-vmmouse-12.4.3/src/vmmouse.c
--- orig/xf86-input-vmmouse-12.4.3/src/vmmouse.c	2007-09-25  
16:11:47.0 -0700
+++ xf86-input-vmmouse-12.4.3/src/vmmouse.c	2008-01-08  
14:58:59.0 -0800

@@ -964,8 +964,11 @@
VMMOUSE_INPUT_DATA  vmmouseInput;
int ps2Buttons = 0;
int numPackets;
+   VMMousePrivPtr mPriv;
+   double factorX, factorY;

pMse = pInfo-private;
+   mPriv = pMse-mousePriv;
while((numPackets = VMMouseClient_GetInput(vmmouseInput))){
   if (numPackets == VMMOUSE_ERROR) {
  VMMouseClient_Disable();
@@ -990,6 +993,13 @@
   dy = vmmouseInput.Y;
   dz = (char)vmmouseInput.Z;
   dw = 0;
+
+  /* X server 1.4.0 does not call VMMouseConvertProc() so we  
scale coordinates here */
+  factorX = ((double) screenInfo.screens[mPriv-screenNum]- 
width) / (double) 65535;
+  factorY = ((double) screenInfo.screens[mPriv-screenNum]- 
height) / (double) 65535;

+  dx = dx * factorX + 0.5;
+  dy = dy * factorY + 0.5;
+
   /* post an event */
   pMse-PostEvent(pInfo, buttons, dx, dy, dz, dw);
}


Oh wow, I owe you a beer!

Any idea why this does not affect everyone using vmware?


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: need Linux help (watch and LVS)

2007-11-04 Thread Sam Lawrance


On 04/11/2007, at 2:33 PM, C Thala wrote:

Can someone tell me the FreeBSD equivalent of the Linux command  
watch.


In Linux, watch is like top, but you can run it against any command
and have it refresh every N seconds. There is a watch command in
FreeBSD but it does something else entirely.


You can do this using a simple shell loop.  If you really need the  
GNU watch command it is available in ports as gnu-watch.


Have a nice day
Sam
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Xorg 7.2 and FreeBSD 6.2-p5 VMWARE vmmouse problem

2007-10-10 Thread Sam Lawrance


On 10/07/2007, at 11:53 AM, Webster, Andrew wrote:


Howdy,



I was successfully able to get Xorg upgraded to 7.2 by just  
installing them from scratch as opposed to trying to upgrading an  
existing system, BUT I’ve run into a problem…




While running VMWare Server 1.0.3 with FreeBSD 6.2-p5 and Xorg 7.2,  
the mouse pointer behaves very oddly.


The pointer appears in the wrong place on the screen for where the  
system actually thinks that it is.


I’m using the vmmouse driver part of the Xorg system, as the  
regular mouse driver doesn’t appear to work at all, unless some  
settings are amiss.


I really like the vmmouse drive because you can move the pointer in/ 
out of the window as you do with regular windows guest OSes.




Has anyone experienced similar problems and/ or know of a fix for  
this?




Andrew,

I just set up VMWare Fusion with FreeBSD and have a problem that  
might be related.  Ascii art time:

_
|_| |
|   |
|   |
|___|

The pointer appears normally on the screen.  However, clicking around  
the screen does not work except in a small area in the top left  
corner.  Moving the mouse within this tiny corner seems to scale up  
and operate on the entire screen.  Eg. if I click and drag across the  
tiny corner, I can see the selection appear across the entire desktop.


Is this similar to your issue?  Did you find a resolution?

Cheers
Sam

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: freebsd 7 release date :)

2007-08-20 Thread Sam Lawrance


On 20/08/2007, at 10:47 AM, Jerry McAllister wrote:


On Sun, Aug 19, 2007 at 03:05:00PM +0200, Wojciech Puchar wrote:




just for reference only:
Original release planned date of 7.0 was end of Jul. But now is  
nearly end

of Aug.
So Which date you guess 7.0 will be released?  :D


when it will be ready. if time is more important than quality for  
you get
simply get -current. even if not - and you would like help testing  
it,

fetch and report problems.


There was obviously no intent to challenge or apply preasure in the
question so you don't need to be snippy.   If you don't have any  
useful
information or at least information you think might be useful  
(qualifier

for my posts) then don't bother replying - at least not snippy, posts.
We can afford to be civil - expecially when a civil question is asked.

The person was just noting that the old guesses were no longer  
operable

and hoping that some new best guesses might have been made.   We all
know these dates are very movable and for very good reasons.   No  
one is

pushing for low quality, hurried up junk.   But those best guesses by
people in the know about how the processes if moving along are helpful
for those of use out here in the hinterland trying to make it through
each day.


There was nothing snippy in that post, it was just succinct.  By now,  
people in the know have learned that it really will be done when  
it's done.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Can't burn cds

2007-07-27 Thread Sam Lawrance


On 27/07/2007, at 12:35 PM, Paul Schmehl wrote:

--On July 26, 2007 5:59:01 PM -0500 Josh Paetzel [EMAIL PROTECTED]  
wrote:


camcontrol isn't going to know anything about IDE devices, it only
knows about SCSI.


So why does it show the first cd, which is also ide?


The device listed by camcontrol seems to be an external hard drive.

That said, I think it's possible for camcontrol to talk to IDE  
devices via atapicam.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: make package-recursive

2007-07-10 Thread Sam Lawrance


On 10/07/2007, at 7:41 PM, Nejc Škoberne wrote:


Hello,

I would like to create a custom set of packages, so that they will
be installable to my other FreeBSD boxen.

As I understand, I have to use 'make package-recursive', but I have
some problems with it:

1. Is there a way to tell 'make package-recursive' not to _install_
   package, but only build it? It is annonying and time-consuming
   to deinstall every package after it is installed.
2. To refer to the previous point: I need to deinstall the packages
   which I 'make package-recursive'-ed before, or else some other
   package which also depends on a port which is already installed
   will not include that (already installed) package. How to change
   this behaviour? I would like that the packages, which I create
   via 'make package-recursive', _always_ include _all_ other
   dependent packages.

Thanks for your help.

P.S.: Do you guys have any scripts for building a customized package
set?



You have to install a package in order to build it, since the package  
is built from the installed files.  Some level of transformation and  
rearrangement occurs during the install process, so there's no easy  
way to package without installing.


You can look in to using tinderbox (available from ports) to build  
packages inside a jail.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Request for CTM assistance

2007-06-06 Thread Sam Lawrance


On 06/06/2007, at 4:23 PM, [EMAIL PROTECTED] wrote:



   My mailer dropped cvs-cur.13428.gz 1/3.



   Could someone who uses CTM forward that e-mail to me at
   [EMAIL PROTECTED]



   Either that or could someone send an e-mail to that address with  
the
   whole file as an attachment?  I don't have FTP access from my  
location
   and it will be months before I'm somewhere I can download it  
myself.


Done!


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD on Apple Mac Mini?

2007-06-03 Thread Sam Lawrance


On 03/06/2007, at 10:26 AM, Richard Tobin wrote:

Does FreeBSD run well on the Mac Mini (x86)?  I'm considering  
getting
one to use for both MacOS and FreeBSD (booting from an external  
disk,

if that's reasonable).



Yep, it works fine.  I used boot camp to create a small boot
partition on the internal drive, and it loads everything else from an
external USB drive.


Thanks.  A few more questions:

 - Any reason to prefer USB over Firewire?


No, it's just what I had.


 - Do you have to use a boot partition on the internal disk?  Can
   FreeBSD boot from external USB or Firewire?


I am not sure.  From what I understand, intel macs can boot from  
either USB or Firewire provided that they are partition using GPT.  I  
used a boot partition on the external disk because I couldn't get it  
to work, and didn't care to spend much time on it.



 - Which release of FreeBSD are you using?


6.2-STABLE.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD on Apple Mac Mini?

2007-06-03 Thread Sam Lawrance


On 03/06/2007, at 8:02 PM, Sam Lawrance wrote:



On 03/06/2007, at 10:26 AM, Richard Tobin wrote:

Does FreeBSD run well on the Mac Mini (x86)?  I'm considering  
getting
one to use for both MacOS and FreeBSD (booting from an external  
disk,

if that's reasonable).



Yep, it works fine.  I used boot camp to create a small boot
partition on the internal drive, and it loads everything else  
from an

external USB drive.


Thanks.  A few more questions:

 - Any reason to prefer USB over Firewire?


No, it's just what I had.


 - Do you have to use a boot partition on the internal disk?  Can
   FreeBSD boot from external USB or Firewire?


I am not sure.  From what I understand, intel macs can boot from  
either USB or Firewire provided that they are partition using GPT.   
I used a boot partition on the external disk because I couldn't get  
it to work, and didn't care to spend much time on it.


s/external/internal/ above :-)


 - Which release of FreeBSD are you using?


6.2-STABLE.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD on Apple Mac Mini?

2007-06-02 Thread Sam Lawrance


On 03/06/2007, at 2:05 AM, Richard Tobin wrote:


Does FreeBSD run well on the Mac Mini (x86)?  I'm considering getting
one to use for both MacOS and FreeBSD (booting from an external disk,
if that's reasonable).


Yep, it works fine.  I used boot camp to create a small boot  
partition on the internal drive, and it loads everything else from an  
external USB drive.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Fix this: The Regents of the University of California. All rights reserved.

2007-05-27 Thread Sam Lawrance


On 27/05/2007, at 1:03 PM, Garrett Cooper wrote:


Kyrre Nygård wrote:

Hello!
Is it possible to change:
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,  
1993, 1994
The Regents of the University of California. All rights  
reserved.

Over to:
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,  
1993, 1994

The Regents of the University of California.
All rights reserved.
If so, how is it done?
To have `All rights reserved.' apply to both copyright statements,  
it is necessary to break it down to the next line. It would also  
look a whole lot neater, as the last number of `1994' now aligns  
with the last letter of `reserved' using a monospaced font, which  
ends up looking kind of weird. Trust me on this one.

Thank you,
Kyrre Nygård + mir-visuals.com + snoarc.no


Now why would you want to do that? That's cutting FreeBSD totally  
out of the picture, which isn't correct since they're the copyright  
owners of the FreeBSD project from 1992 to today.


I think the point is to reformat the all rights reserved statement,  
rather than remove a copyright line.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: gnome-libtool issue [SEC=UNCLASSIFIED]

2007-05-16 Thread Sam Lawrance


On 16/05/2007, at 9:31 AM, Daniel Pottumati wrote:



No, I wish I could upgrade.

But for compatibility reasons with one piece of software here at  
work, I have to run 4.8...


Any other sugestions???


Perhaps if you explained the compatibility issues, we can help you  
work around those.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: gnome-libtool issue [SEC=UNCLASSIFIED]

2007-05-15 Thread Sam Lawrance


On 15/05/2007, at 11:29 AM, Daniel Pottumati wrote:


Hello,

I've a 4.8 freebsd box, which I've update the ports tree with the  
current

tree from the freebsd website and I'm trying to install tetex from the
port directory:

/usr/ports/print/teTeX

 and I get the following error during: make install

/bin/sh /usr/ports/x11-fonts/fontconfig/work/gnome-libtool --tag=CC
--mode=compile cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src
-I/usr/local/include/freetype2 -I/usr/local/include  -I/usr/local/ 
include

-Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations  -Wnested-externs -fno-strict-aliasing
-DFC_CACHEDIR='/var/db/fontconfig'
-DFONTCONFIG_PATH='/usr/X11R6/etc/fonts'-O -pipe  -c -o  
fcatomic.lo

fcatomic.c
gnome-libtool: unrecognized option `--tag=CC'

Try `gnome-libtool --help' for more information.

gmake[3]: *** [fcatomic.lo] Error 1
gmake[3]: Leaving directory
`/usr/ports/x11-fonts/fontconfig/work/fontconfig-2.4.2/src'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/x11-fonts/fontconfig/work/fontconfig-2.4.2/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/x11-fonts/fontconfig/work/fontconfig-2.4.2'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/x11-fonts/fontconfig.
*** Error code 1

Stop in /usr/ports/x11/XFree86-4-libraries.
*** Error code 1

Stop in /usr/ports/x11-fonts/p5-type1inst.
*** Error code 1

Stop in /usr/ports/print/cmpsfont.
*** Error code 1

Stop in /usr/ports/print/teTeX-texmf.
*** Error code 1

Stop in /usr/ports/print/teTeX.

Can someone help me please?


Are  you able to upgrade the machine?  FreeBSD 4.x is no longer  
supported, and 4.8 is very old.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Skipping F1 FreeBSD prompt on boot

2007-05-15 Thread Sam Lawrance


On 14/05/2007, at 10:41 AM, Pieter de Goeje wrote:


On Sunday 13 May 2007, David Landgren wrote:

Sam Lawrance wrote:

On 13/05/2007, at 6:15 PM, Matthew Seaman wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Sam Lawrance wrote:

On 12/05/2007, at 8:59 PM, Matthew Seaman wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

David Landgren wrote:
I have a disk that has only FreeBSD on it, and so I would  
like to

skip the initial F1/FreeBSD prompt. boot0cfg -v ad0 says:

options=nopacket,update,nosetdrv
default_selection=F1 (Slice 1)

... what do I have to do to say JFDI instead of prompting?  
This is
not the sort of thing I want to fiddle around experimenting,  
so a

little guidance would be most appreciated.


fdisk -B -b /boot/mbr /dev/ad0

You installed the FreeBSD boot sector stuff, which gives you the
'press F1'  business.  Replace that with the standard mbr,  
which just

boots straight up.


Rather than replacing it, you can use boot0cfg to set a really  
short
timeout instead; in case you might want that functionality one  
day.


Heh.  It's not like you only get one chance to rewrite the boot  
blocks
on any particular drive.  If anyone needs to (re-)install the  
FreeBSD

boot
blocks, then you can do very simply it by:

   boot0cfg -B -b /boot/boot0 /dev/ad0

or even

   fdisk -B -b /boot/boot0 /dev/ad0

Or if you need to boot from a serial console you can change / 
boot/boot0

to /boot/boot0sio


Sure, but why get rid of it, when leaving it in with a short timeout
costs you nothing.


A fair point, but in this particular case, FreeBSD is the only  
thing on

the drive, and likely to remain that way until the disk dies of
mechanical failure. I just don't need that prompt, especially the
annoying beep it makes.

The beep was removed since May 2006 (6.2-RELEASE, 6-STABLE, HEAD).
A simple
#boot0cfg -B /dev/adX
should get rid of it.


I thought I remembered that!  Wasn't it removed to reclaim a couple  
extra bytes? :-)


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Skipping F1 FreeBSD prompt on boot

2007-05-13 Thread Sam Lawrance


On 12/05/2007, at 8:59 PM, Matthew Seaman wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

David Landgren wrote:

I have a disk that has only FreeBSD on it, and so I would like to  
skip

the initial F1/FreeBSD prompt. boot0cfg -v ad0 says:

options=nopacket,update,nosetdrv
default_selection=F1 (Slice 1)

... what do I have to do to say JFDI instead of prompting? This is  
not

the sort of thing I want to fiddle around experimenting, so a little
guidance would be most appreciated.


fdisk -B -b /boot/mbr /dev/ad0

You installed the FreeBSD boot sector stuff, which gives you the  
'press

F1'  business.  Replace that with the standard mbr, which just boots
straight up.



Rather than replacing it, you can use boot0cfg to set a really short  
timeout instead; in case you might want that functionality one day.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Skipping F1 FreeBSD prompt on boot

2007-05-13 Thread Sam Lawrance


On 13/05/2007, at 6:15 PM, Matthew Seaman wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Sam Lawrance wrote:


On 12/05/2007, at 8:59 PM, Matthew Seaman wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

David Landgren wrote:

I have a disk that has only FreeBSD on it, and so I would like  
to skip

the initial F1/FreeBSD prompt. boot0cfg -v ad0 says:

options=nopacket,update,nosetdrv
default_selection=F1 (Slice 1)

... what do I have to do to say JFDI instead of prompting? This  
is not
the sort of thing I want to fiddle around experimenting, so a  
little

guidance would be most appreciated.


fdisk -B -b /boot/mbr /dev/ad0

You installed the FreeBSD boot sector stuff, which gives you the  
'press

F1'  business.  Replace that with the standard mbr, which just boots
straight up.



Rather than replacing it, you can use boot0cfg to set a really short
timeout instead; in case you might want that functionality one day.


Heh.  It's not like you only get one chance to rewrite the boot blocks
on any particular drive.  If anyone needs to (re-)install the  
FreeBSD boot

blocks, then you can do very simply it by:

   boot0cfg -B -b /boot/boot0 /dev/ad0

or even

   fdisk -B -b /boot/boot0 /dev/ad0

Or if you need to boot from a serial console you can change /boot/ 
boot0

to /boot/boot0sio


Sure, but why get rid of it, when leaving it in with a short timeout  
costs you nothing.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Network interface restart

2007-05-09 Thread Sam Lawrance


On 09/05/2007, at 8:31 PM, Bram Schoenmakers wrote:


Hi,

I tried to reduce the MTU of a network interface on a remote  
FreeBSD 6.2

machine.

So that means changing this line in rc.conf:

ifconfig_bge0=inet xxx.xxx.xxx.xxx netmask 255.255.255.128

to

ifconfig_bge0=inet xxx.xxx.xxx.xxx netmask 255.255.255.128 mtu 1472

Of course, there's a real IP address set.

Then, I tried to restart the network interface:

/etc/rc.d/netif restart

which went horribly wrong. I lost connection and wasn't able to  
reconnect. I
tried to run this in some 'fallback' script, which automatically  
should
restore the old configuration and restarting the network interface  
again
after 5 minutes. Even if that failed, it should reboot the machine.  
But
somehow the script was aborted, although I ran it in a 'screen'  
session over
SSH. So the last resort  was a manual reboot, which started the  
interface

with MTU 1472 just fine.

Could someone please point out where I made the mistake?


When your network interface went down, you lost the connection, your  
shell lost the terminal and your script was terminated before it  
could finish doing what it was supposed to.  Possibly you need to use  
something like nohup or screen (from ports), or have some other  
form of terminal available.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Greylisting -- Was: Anti Spam

2007-04-28 Thread Sam Lawrance


On 28/04/2007, at 7:25 PM, Ted Mittelstaedt wrote:





-Original Message-
From: Bart Silverstrim [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 1:58 PM
To: Ted Mittelstaedt
Cc: Christopher Hilton; Grant Peel; Eric Crist;
freebsd-questions@freebsd.org
Subject: Re: Greylisting -- Was: Anti Spam



On Apr 26, 2007, at 12:15 AM, Ted Mittelstaedt wrote:


There are legitimate technical reasons that someone may want their
mail
to not be greylisted.  For example, my cell phone's e-mail  
address is
in our monitoring scripts to page me in the event of a server  
failure.

I would be pretty pissed off if Sprint suddenly started
greylisting.  It
isn't just dumb-ass users making stupid political decisions to  
reject

it, although in your case it probably was.


If it is a legitimate mail server, it would be promoted to the auto-
whitelist.  Not all mail is constantly greylisted by most intelligent
greylist systems.  Only the first few messages would be delayed,
until it is established as legitimate.



That won't work in my case since I generally only have a failure  
that causes
a problem which results in paging about once every 3 months or so.   
By the

 time the pages got through the
greylist it would be at least an hour later after the system had gone
down.  That isn't acceptable for a notification system.


Email is not an instant messaging system, no matter how much you want  
it to be one.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Fetching sources from Windows?

2007-04-07 Thread Sam Lawrance


On 31/03/2007, at 12:57 AM, Joe Kraft wrote:


Jerry McAllister wrote:

On Mon, Mar 05, 2007 at 12:45:55PM -0500, frzburn wrote:

Hi!
I have a slow Internet connection at home, and I would like to  
know if it is
possible to fetch the STABLE sources from somewhere else (ex.: at  
work).
What I want is to get the latest sources, like described in the  
handbook (
http://www.ca.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ 
synching.html),
even if it means downloading all of it, since there no way to  
diff with my

current source...
Basically, that is what I do.  I only have a regular old phone  
modem at home.
I take my home machine in to the office where I have a reliable  
100 Mb/s
and do my installs there.   The only problem is fixing up IPs and  
host

names.
If I ever get rich and get a laptop with significant disk, I can just
carry that and pull everything down to it and take it home to work
on the desktop machine - or I could get one of those nice big USB  
drives

and download everything to that.
jerry
I have a computer that's not connected to the internet that I keep  
up to date using CTM.  I've subscribed to one of the ctm-XXX mail  
list with my work address and I just save the messages to a  
relatively small USB memory stick from the windows machine.  Once I  
have the updates on there I bring the stick home and run ctm-rmail  
and it updates my source tree.


It would have been even easier if I was able to get ftp access to  
get the CTM updates directly without resorting to using e-mail for  
the transfer.


You can!  The CTM deltas are available from FTP.  You would have  
started out by getting an empty delta from FTP - and all the  
increments are located in the same place.  There is more information  
in the handbook.


Cheers
Sam

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Citrix ICA client problems - no keyboard response (weirdness)

2003-09-26 Thread Sam Lawrance
Hi,

I'm using the citrix ica client from ports to connect to a w2k server,
and I'm seeing some weird behaviour. Almost all aspects of the
connection seem fine - I can connect, get a logon screen, and if I
supply credentials on the command line the login goes like it should.

However, keyboard activity doesn't seem to be working. I can see the
data going out when I type; but no response. Eg. at the logon screen, I
can't type my username, tab between fields or anything.

Any ideas or suggestions of what to do next appreciated.

Regards
Sam Lawrance.
(please cc replies my way)

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Fixed - Citrix ICA client problems - no keyboard response (weirdness)

2003-09-26 Thread Sam Lawrance
Problem solved - all I had to do was set the client keyboard type
(netbsd worked for me) in Tools - Settings

Regards
Sam.



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


How to structure a port with plugins

2003-08-18 Thread Sam Lawrance
Hi all, (please cc replies to me)

I'm writing a port for multisync. Included in the source tarball are a
bunch of plugins for synchronising with various devices and programs.
Not everbody is going to want them all. There's no existing mechanism to
automatically build some or all of the plugins.

What is the best way to build the plugins?

I've thought of the doing the following:
- Have a separate port for each plugin, depend on the main port for the
source. This sure makes creating the packing list a lot simpler.
- Build the plugins from the main port based in WITH_x variables

Now I think about it the first option seems better, but I'd like to hear
what anybody thinks.

Thanks,
-Sam Lawrance.



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]