Re: X.org problems

[Guillermo Garcia-Rojas]

On 10/10/05, Kent Stewart <[EMAIL PROTECTED]> wrote:
>
> On Monday 10 October 2005 03:38 pm, Guillermo Garcia-Rojas wrote:
> > I have cvsuped today from 5.4-STABLE to 6.0-RC1 and when I do
> > "startx" the machine reboots. I have deinstalled the ports and build
> > again the X.org <http://X.org><http://X.org>distribution.
> > Any ideas?
> >
>
> I was reading where some of the system libraries were changed going to
> 6.x. So, did you rebuild your ports?
>
> Kent
>
> --
> Kent Stewart
> Richland, WA
>
> http://users.owt.com/kstewart/index.html
>

I've rebuild only x.org <http://x.org> ports, maybe I need to rebuild some
other ports like imake.

--
---
Guillermo García Rojas Covarrubias
Director General
SoloBSD
http://SoloBSD.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

X.org problems

[Guillermo Garcia-Rojas]

I have cvsuped today from 5.4-STABLE to 6.0-RC1 and when I do "startx" the
machine reboots. I have deinstalled the ports and build again the
X.orgdistribution.
Any ideas?

--
---
Guillermo García Rojas Covarrubias
Director General
SoloBSD
http://SoloBSD.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

More on X.org Problems

[Guillermo Garcia-Rojas]

It seems something is wrong in latest version of X.org , many
people are reporting the same issue with it that I have days ago.

The issue is that when upgrading to X.org  6.8.2 and running
X, the screen goes blsck and the machine reboots, this has been confirmed on
users from Fedora and my experience with FreeBSD 6.0-BETA4 and 5. Now I'm
running FreeBSD 5.4-STABLE with X.org  6.7.x and all is going
fine, but in a few hours I'm gonna update to newest version on ports.

Anyone running latest X.org  and having this problem too?

Thanks!

--
---
Guillermo García Rojas Covarrubias
Director General
SoloBSD
http://SoloBSD.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: X.org

[Guillermo Garcia-Rojas]

here it is: (from Sept 13th, it doesn't create another since that date)

(**) FontPath set to 
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TT
F/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(**) ModulePath set to "/usr/X11R6/lib/modules"
(--) Chipset SIS630/730 found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe0 - 0x (0x20) MX[B](B)
[1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B)
[2] -1 0 0x000f - 0x000f (0x1) MX[B]
[3] -1 0 0x000c - 0x000e (0x3) MX[B]
[4] -1 0 0x - 0x0009 (0xa) MX[B]
[5] -1 0 0xcfffe000 - 0xcfff (0x2000) MX[B]E
[6] -1 0 0xcfffd000 - 0xcfffdfff (0x1000) MX[B]E
[7] -1 0 0xcfffc000 - 0xcfffcfff (0x1000) MX[B]E
[8] -1 0 0xcfff7000 - 0xcfff7fff (0x1000) MX[B]E
[9] -1 0 0xd000 - 0xcfff (0x0) MX[B]EO
[10] -1 0 0xcfee - 0xcfef (0x2) MX[B](B)
[11] -1 0 0xc000 - 0xc7ff (0x800) MX[B](B)
[12] -1 0 0x - 0x (0x1) IX[B]
[13] -1 0 0x - 0x00ff (0x100) IX[B]
[14] -1 0 0xd400 - 0xd4ff (0x100) IX[B]E
[15] -1 0 0xd800 - 0xd8ff (0x100) IX[B]E
[16] -1 0 0xd000 - 0xd0ff (0x100) IX[B]E
[17] -1 0 0xcc00 - 0xccff (0x100) IX[B]E
[18] -1 0 0xff00 - 0x (0x100) IX[B]E
[19] -1 0 0xac00 - 0xac7f (0x80) IX[B](B)
(II) resource ranges after probing:
[0] -1 0 0xffe0 - 0x (0x20) MX[B](B)
[1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B)
[2] -1 0 0x000f - 0x000f (0x1) MX[B]
[3] -1 0 0x000c - 0x000e (0x3) MX[B]
[4] -1 0 0x - 0x0009 (0xa) MX[B]
[5] -1 0 0xcfffe000 - 0xcfff (0x2000) MX[B]E
[6] -1 0 0xcfffd000 - 0xcfffdfff (0x1000) MX[B]E
[7] -1 0 0xcfffc000 - 0xcfffcfff (0x1000) MX[B]E
[8] -1 0 0xcfff7000 - 0xcfff7fff (0x1000) MX[B]E
[9] -1 0 0xd000 - 0xcfff (0x0) MX[B]EO
[10] -1 0 0xcfee - 0xcfef (0x2) MX[B](B)
[11] -1 0 0xc000 - 0xc7ff (0x800) MX[B](B)
[12] 0 0 0x000a - 0x000a (0x1) MS[B]
[13] 0 0 0x000b - 0x000b7fff (0x8000) MS[B]
[14] 0 0 0x000b8000 - 0x000b (0x8000) MS[B]
[15] -1 0 0x - 0x (0x1) IX[B]
[16] -1 0 0x - 0x00ff (0x100) IX[B]
[17] -1 0 0xd400 - 0xd4ff (0x100) IX[B]E
[18] -1 0 0xd800 - 0xd8ff (0x100) IX[B]E
[19] -1 0 0xd000 - 0xd0ff (0x100) IX[B]E
[20] -1 0 0xcc00 - 0xccff (0x100) IX[B]E
[21] -1 0 0xff00 - 0x (0x100) IX[B]E
[22] -1 0 0xac00 - 0xac7f (0x80) IX[B](B)
[23] 0 0 0x03b0 - 0x03bb (0xc) IS[B]
[24] 0 0 0x03c0 - 0x03df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/X11R6/lib/modules/libvbe.a
(II) Module vbe: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 0.7
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/libint10.a
(II) Module int10: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) SIS(0): initializing int10
(==) SIS(0): Write-combining range (0xa,0x2) was already clear
(==) SIS(0): Write-combining range (0xc,0x4) was already clear
(II) SIS(0): Primary V_BIOS segment is: 0xc000
(==) SIS(0): Write-combining range (0x0,0x1000) was already clear
(II) SIS(0): VESA BIOS detected
(II) SIS(0): VESA VBE Version 3.0
(II) SIS(0): VESA VBE Total Mem: 8192 kB
(II) SIS(0): VESA VBE OEM: SiS
(II) SIS(0): VESA VBE OEM Software Rev: 1.0
(II) SIS(0): VESA VBE OEM Vendor:
(II) SIS(0): VESA VBE OEM Product:
(II) SIS(0): VESA VBE OEM Product Rev:
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) SIS(0): VESA VBE DDC supported
(II) SIS(0): VESA VBE DDC Level 2
(II) SIS(0): VESA VBE DDC transfer in appr. 1 sec.
(II) SIS(0): VESA VBE DDC read successfully
(==) SIS(0): Write-combining range (0x0,0x1000) was already clear


Xorg detected your mouse at device /dev/sysmouse.
Please check your config if the mouse is still not
operational, as by default Xorg tries to autodetect
the protocol.

Your xorg.conf file is /root/xorg.conf.new

To test the server, run 'X -xf86config /root/xorg.conf.new'

On 9/19/05, Garrett Cooper <[EMAIL PROTECTED]> wrote:
> 
> Guillermo Garcia-Rojas wrote:
> 
> >On 9/15/05, Garrett Cooper <[EMAIL PROTECTED]> wrote:
> >
> >
> >>On Sep 15, 2005, at 12:40 PM, Guillermo Garcia-Rojas wrote:
> >>
> >>
> >>
> >>>I'm using FreeBSD 6.0-BETA4 and I'm having some trou

Re: X.org

[Guillermo Garcia-Rojas]

On 9/15/05, Garrett Cooper <[EMAIL PROTECTED]> wrote:
> 
> On Sep 15, 2005, at 12:40 PM, Guillermo Garcia-Rojas wrote:
> 
> > I'm using FreeBSD 6.0-BETA4 and I'm having some troubles with
> > X.org <http://X.org><http://X.org>xonfiguration, I have a SiS 630/730 
> video card and
> > my mouse doesn't work on
> > console. When I launch "startx" the screen goes blank and the machine
> > reboots.
> >
> > This is my xorg.conf file.
> 
> > --
> > ---
> > Guillermo García Rojas Covarrubias
> > Director General
> > SoloBSD
> > http://SoloBSD.org
> 
> What does it say in the Xorg logfile?
> -Garrett



It doesn't log anything bad. I have Xorg.0.log from September 13th and it 
doesn't modify when I run "startx"
At the end of the file it says that Xorg detected my mouse at /dev/sysmouse 
and that my xorg.conf file is /root/xorg.conf.new etc. etc.

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



-- 
---
Guillermo García Rojas Covarrubias
Director General 
SoloBSD
http://SoloBSD.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

X.org

[Guillermo Garcia-Rojas]

I'm using FreeBSD 6.0-BETA4 and I'm having some troubles with
X.orgxonfiguration, I have a SiS 630/730 video card and
my mouse doesn't work on
console. When I launch "startx" the screen goes blank and the machine 
reboots.

This is my xorg.conf file.

Thanks!


Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/URW"
FontPath "/usr/X11R6/lib/X11/fonts/freefont"
FontPath "/usr/X11R6/lib/X11/fonts/artwiz-fonts"
FontPath "/usr/X11R6/lib/X11/fonts/koi8-u-gemini"
FontPath "/usr/X11R6/lib/X11/fonts/local/sgi"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "glx"
Load "record"
Load "xtrap"
Load "speedo"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "es"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/sysmouse"
Option "Buttons" "5"
EndSection

Section "Monitor"

#DisplaySize 280 210 # mm
Identifier "Monitor0"
VendorName "DWE"
ModelName "Daewoo 531X"
HorizSync 30.0 - 54.0
VertRefresh 50.0 - 120.0
Option "DPMS"
EndSection

Section "Device"

### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor" # []
#Option "HWcursor" # []
#Option "NoAccel" # []
#Option "TurboQueue" # []
#Option "FastVram" # []
#Option "NoHostBus" # []
#Option "ForceCRT2Type" # []
#Option "ShadowFB" # []
#Option "Rotate" # []
#Option "NoXvideo" # []
#Option "Vesa" # []
#Option "MaxXFBMem" # 
#Option "ForceCRT1" # []
#Option "DSTN" # []
#Option "XvOnCRT2" # []
#Option "PanelDelayCompensation" # 
#Option "TVStandard" # 
#Option "UseROMData" # []
#Option "NoInternalModes" # []
#Option "UseOEMData" # []
#Option "BIOSFile" # 
#Option "NoYV12" # []
#Option "CHTVType" # []
#Option "CHTVOverscan" # []
#Option "CHTVSuperOverscan" # []
#Option "CHTVLumaBandwidthCVBS" # 
#Option "CHTVLumaBandwidthSVIDEO" # 
#Option "CHTVLumaFlickerFilter" # 
#Option "CHTVChromaBandwidth" # 
#Option "CHTVChromaFlickerFilter" # 
#Option "CHTVCVBSColor" # []
#Option "CHTVTextEnhance" # 
#Option "CHTVContrast" # 
#Option "SISTVEdgeEnhance" # 
#Option "SISTVAntiFlicker" # 
#Option "SISTVSaturation" # 
#Option "TVXPosOffset" # 
#Option "TVYPosOffset" # 
#Option "SIS6326TVAntiFlicker" # 
#Option "SIS6326TVEnableYFilter" # []
#Option "SIS6326TVYFilterStrong" # []
#Option "UseColorHWCursor" # []
#Option "ColorHWCursorBlending" # []
#Option "ColorHWCursorBlendThreshold" # 
#Option "RestoreBySetMode" # []
Identifier "Card0"
Driver "sis"
VendorName "Silicon Integrated Systems [SiS]"
BoardName "SiS630 GUI Accelerator+3D"
ChipSet "SIS630/730"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

-- 
---
Guillermo García Rojas Covarrubias
Director General 
SoloBSD
http://SoloBSD.org
___
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 remove empty directory

[Guillermo Garcia-Rojas]

I suffered the same problem with 2 ports, I couldn't delete them, nor
"make clean". I decide to rename (mv) the port. I build the ports and
when I rebooted the box, when it cames to the part of checking the
filesystem; it automagically fix the corruption. And I deleted the
renamed ports :)

When I tried to delete the ports it says something like:

#foo.bar: bad file descriptor. 

On 4/12/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 12, 2005 at 05:42:14PM -0500, Guillermo Garcia-Rojas wrote:
> > After moving the directory, the system will prompt for a corruption on
> > the filesystem and a simple fsck, as you say, will fix the problem :)
> 
> I don't know what you mean by "prompt for a corruption".
> 
> Kris
> 
> 
> 


-- 
---
Guillermo García Rojas Covarrubias
Director General 
SoloBSD
http://www.solobsd.org
___
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 remove empty directory

[Guillermo Garcia-Rojas]

After moving the directory, the system will prompt for a corruption on
the filesystem and a simple fsck, as you say, will fix the problem :)

These are my 2 cents.

On 4/12/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 12, 2005 at 12:14:12PM -1000, Robert Marella wrote:
> 
> > drwxr-xr-x  3 root  wheel  1024 Apr 12 10:06 .
> > drwxr-xr-x  3 root  wheel   512 Apr 12 10:06 ..
> > drwxr--r--  4 root  wheel 0 Apr 12 09:51 gail
> > p4# chflags -R noschg gail
> > p4# rm -r gail
> > rm: gail: Directory not empty
> > p4# rm gail
> > rm: gail: is a directory
> > p4# rmdir gail
> > rmdir: gail: Directory not empty
> > p4#
> >
> > The obvious problem is that the number of links is incorrect but I don't
> > know how to make that right.
> >
> > Any help is greatly appreciated.
> 
> Unmount the filesystem and run fsck to repair the filesystem
> corruption.
> 
> Kris
> 
> 
> 


-- 
---
Guillermo García Rojas Covarrubias
Director General 
SoloBSD
http://www.solobsd.org
___
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 remove empty directory

[Guillermo Garcia-Rojas]

move it, I just had an issue like that

cd /usr/ports/accessibility
mv gail gail2 (in example)

then you cvsup the ports again and it's done.

On 4/12/05, Robert Marella <[EMAIL PROTECTED]> wrote:
> Greetings
> 
> I think this problem occurred during "portmanager -u" but I can't be
> certain. Portmanager  did a core dump this morning. I tried a portsclean
> -CD and /usr/ports/accessibility/gail/work cannot be removed. Here is
> what I have tried.
> 
> p4# cd /usr/ports/accessibility/gail
> p4# ls -l
> total 14
> -rw-r--r--  1 root  wheel   920 Apr 12 02:21 Makefile
> -rw-r--r--  1 root  wheel   109 Apr 12 02:21 distinfo
> drwxr-xr-x  2 root  wheel   512 Nov 10 20:16 files
> -rw-r--r--  1 root  wheel   211 Apr  4  2004 pkg-descr
> -rw-r--r--  1 root  wheel  2667 Apr 12 02:21 pkg-plist
> drwxr-xr-x  3 root  wheel   512 Apr 12 10:06 work
> p4# rm -r work
> rm: work/gail-1.8.3/gail: Directory not empty
> rm: work/gail-1.8.3: Directory not empty
> rm: work: Directory not empty
> p4# cd work/gail-1.8.3/gail/
> p4# ls -la
> total 0
> p4# cd ..
> p4# ls -la
> total 4
> drwxr-xr-x  3 root  wheel  1024 Apr 12 10:06 .
> drwxr-xr-x  3 root  wheel   512 Apr 12 10:06 ..
> drwxr--r--  4 root  wheel 0 Apr 12 09:51 gail
> p4# chflags -R noschg gail
> p4# rm -r gail
> rm: gail: Directory not empty
> p4# rm gail
> rm: gail: is a directory
> p4# rmdir gail
> rmdir: gail: Directory not empty
> p4#
> 
> The obvious problem is that the number of links is incorrect but I don't
> know how to make that right.
> 
> Any help is greatly appreciated.
> 
> Robert
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


-- 
---
Guillermo García Rojas Covarrubias
Director General 
SoloBSD
http://www.solobsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: hyper threading.

[Guillermo Garcia-Rojas]

Stop feeding this troll, he has been banned from de DragonFly BSD list
for his stupid comments, his e-mail address doesn't even exist. His
only goal is make the longest thread of messages in history.

Stop him!

On Tue, 29 Mar 2005 14:54:30 -0500, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Thats because you seem unable to grasp modern
> concepts. If you think that performance criteria
> of modern controllers and processors are the same
> as 30 years ago, then you are incapable of commenting
> on anything modern. Every controller/processor is
> different and has its own advantages and inefficiencies.
> The fact that you can make ignorant statements like
> "I proved polling is faster because 20 years ago I wrote
> a driver", then you think that you know things that you
> don't.
> 
> -Original Message-
> From: Anthony Atkielski <[EMAIL PROTECTED]>
> To: freebsd-questions@freebsd.org
> Sent: Tue, 29 Mar 2005 21:02:40 +0200
> Subject: Re: hyper threading.
> 
> [EMAIL PROTECTED] writes:
> 
> > If you think that then you are either a fool or
> > an old fool..
> 
> I've never encountered a situation in which experience was a
> disadvantage.
> 
> --
> Anthony
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


-- 
---
Guillermo García Rojas Covarrubias
Director General 
SoloBSD
http://www.solobsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Please don't change Beastie to another crap logo such as NetBSD!!!

[Guillermo Garcia-Rojas]

I think we all are happy with beastie, there is no reason to change
it, if some idiots think it's evil, that's their problem.

I hope no one sends a new logo for the contest, and if what FreeBSD
Project wants is a new "FreeBSD" type of font, or style, then do it,
but don't blow beastie away.

It would be better to give beastie a BSD license :)

On Wed, 9 Feb 2005 20:29:18 +0100, Oliver Leitner <[EMAIL PROTECTED]> wrote:
> "if we dont take care of the little things around us, what right do we have
> to be upset on the bigger ones?"
> 
> On Wednesday 09 February 2005 20:28, sp0ng3b0b wrote:
> > Charles-André Landemaine wrote:
> > > This will sign the death of FreeBSD.
> > > Oh please, wake me up, it's a nightmare!!!
> >
> > Come on now, is changing the logo ALL that BAD? Companies and
> > organizations do it all the time. Who cares? It's not like a new logo
> > will introduce new bugs and vulnerabilities in your OS!
> >
> > Change is good. Time to try something different. I think some folks
> > should relax and not get too upset. There are worse things going on in
> > the world...
> >
> > ...my 2 cents...
> > ___
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "[EMAIL PROTECTED]"
> 
> --
> By reading this mail you agree to the following:
> 
> using or giving out the email address and any
> other info of the author of this email is strictly forbidden.
> By acting against this agreement the author of this mail
> will take possible legal actions against the abuse.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


-- 
---
Guillermo García Rojas Covarrubias
Director General 
SoloBSD
http://www.solobsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"