Re: Is it worthy upgrading to 9.0 ?

[Allen]

On 2/28/2012 3:03 AM, Damien Fleuriot wrote:
> This is an entirely subjective question and one that only you can answer.
> 
> For example, given the number of problem reports I'm seeing on the
> lists, I'm going to stick with the 8-STABLE branch for still a long
> time, likely until 9.1 or 9.2-RELEASE.

I don't think it's a good idea to let what you see on a mailing list be
your end all be all of what you use... This isn't an insult or anything,
but I've seen some pretty damn stupid people who try to install stuff
into Swap And that isn't even close to the stupidest thing I've ever
seen on a list. Trust me, the best way to figure out of you personally
would benefit from upgrading, is doing it yourself.

I use and read these lists, and I admit, sometimes, it's for
entertainment value, but again, I've also received more than my share of
help from people who DO know WTF they're doing.

It doesn't cost you more than a CD or DVD, so why not just download 9
and try it out? I have every version of FreeBSD I've ever downloaded, or
paid for, starting with 4.0 back in 2000 or so, and I am now running 9.0
on my main FreeBSD machine, and PC-BSD 8.2 on a Desktop, and PC-BSD 9 on
my Laptop. I've had NO issues with any of them.

So for whatever it's worth to you; I am using FreeBSD 9.0-RELEASE, and I
like it.

-Allen
___
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.4.rc6 (32bit Wine for 64bit FreeBSD)

[David Naylor]

On Tuesday, 6 March 2012 00:01:48 Mehmet Erol Sanliturk wrote:
> On Mon, Mar 5, 2012 at 3:00 PM, David Naylor 
wrote:
> > On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote:
> > > On Mon, Mar 5, 2012 at 6:55 AM, David Naylor
> > 
> > wrote:
> > > > Please include the full error message, also could you please try
> > 
> > running
> > 
> > > > those apps in a clean wine prefix.
> > > 
> > > # pwd
> > > /root/APPLY/PROGRAMS
> > > 
> > > # wine x.exe
> > > 
> > > err : module : LdrInitializeThunk Main exe initialization for
> > > L"F:\\APPLY\\PROGRAMS\\x.exe" failed , status c017
> > 
> > I have tried to reproduce the error on my side but was unable to.  The
> > programs that I tested work without error.
> 
> This means that there are additional parts in your system which they do not
> exist here .
> Such parts are not added by "pkg_add wine-fbsd64 ..." .
> I do not have any idea about which parts may be missing .

It could also mean there are extra components on your computer that are 
interfering however using a clean wine prefix (as mentioned below) has ruled 
that out.  

> > I was expecting more output from wine...  Please see below about using a
> > clean
> > wine prefix.  Do you use the nvidia graphics driver?  If so please run
> > (as root), and provide the output:
> > # sh /usr/local/share/wine/patch-nvidia.sh
> 
> There is NO nvidia grphics driver . It is Intel DG965WH main board with its
> integrated graphics driver .

That eliminates my only other idea.  

> > If nothing fixes your problem then please submit a bug report at
> > bugs.winehq.org.
> > 
> > > I could not understand the phrase :
> > > 
> > > "in a clean wine prefix" .
> > 
> > To run a program in a clean wine prefix do:
> > env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe
> 
> This is NOT changing the error message . Only drive become Z: .

As mentioned above, eliminates possible extra components causing interference.  

> > You may need to use winetricks to install some support programs.
> > 
> > Good luck
> 
> "winetricks" could NOT be found .

Please see http://wiki.winehq.org/winetricks for details about winetricks.  

> I tried wine which is added by
> 
> pkg_add -r wine
> 
> from packages
> 
> in FreeBSD 9.0 RELEASE i386 as it is installed .
> 
> On the same programs , the message is the same with amd64 message .

To clarify: you tried running the program under an i386 installation of 
FreeBSD and wine gave you the same problem?  

Also, has a previous version of wine ever worked for your program?  Could you 
try installing an older version of wine (the mediafire page contains wine 
releases going back to 1.3.16).  

Regards


signature.asc
Description: This is a digitally signed message part.

Needs GSOC project idea guide.

[Tiwari Punit]

Hello,
I, Punit Tiwari, pursing final year BE(IT) student.

Final year project "Game Engine":
Project Description:

 Platform

Java

Application Framework

Javafx 2.0

Database

DB2

Game Type

2D RPG Game

User

Any (knows to use computer)

Prsently, this game engine build 2d games like mario, countra, for the user
who doesn't knows programming language.

Please, suggest is this project can be given for GSOC, if not plz suggest
me some project idea.

Thank you,
Punit Tiwari
___
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: semi OT: correct CIDR block?

[Michael Sierchio]

ipsc, from packages or ports, is very useful.

> ipsc -gch 10.0.0.32/27
Network class:A
Network mask: 255.0.0.0
Network mask (hex):   FF00
Network address:  10.0.0.32
Subnet bits:  19
Max subnets:  524288
Full subnet mask: 255.255.255.224
Full subnet mask (hex):   FFE0
Host bits:5
Hosts per subnet: 32
Bit map:  ...sssh

IP address:   10.0.0.32
Hexadecimal IP address:   A20
Address allocation range: 10.0.0.32  - 10.0.0.63
Full subnet mask: 255.255.255.224
Subnet mask:  0.255.255.224
Subnet ID:0.0.0.32
Network ID:   10.0.0.0
Host ID:  0.0.0.32

Cisco Wildcard:   0.0.0.31
CIDR notation:10.0.0.0  /27
Route/Mask:   10.0.0.0   / 255.255.255.224
Hexadecimal route/mask:   A00/ FFE0
Supernet max: 0

On Mon, Mar 5, 2012 at 6:51 AM, Tim Kellers  wrote:

> On 03/05/12 09:30, Robert Huff wrote:
>
>>With my brain still on EBADSLEEP, I cannot decide if:
>>
>>10.0.0.32-10.0.0.63
>>
>>is correctly described by:
>>
>>10.0.0.32/27
>>
>>Anyone?  Please?
>>
>>
>>Robert Huff
>>
>> __**_
>> 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 "
>>
>
>   Network = 10.0.0.32
> Usable IPs = 10.0.0.33 to 10.0.0.62 for 30
>  Broadcast = 10.0.0.63
>   Netmask = 255.255.255.224
> Wildcard Mask = 0.0.0.31
>
>
>
> Looks pretty good to me.
>
> Tim Kellers
>
>
> __**_
> 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 "
>
___
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: [spam] Equine Vaccines offered by Santa Cruz

[Robert Bonomi]

Anyone offended by this spam to the mailing-list is strongly encouraged
to call the company to complain -- TOLL FREE numbers are:
   U.S.A.   1-800-457-3801  (headquarters)
   Europe   +00800 4573 8000(Germany)
   Asia (010) 800.40402026  (Japan)
   Asia 00798.1.1.002.0297  (S. Korea)

In North America, using a pay phone costs the toll-free owner over $0.35
when they answer the call.  Keep this in mind if you have to call back 
because of a dropped connection, or other communication problem.,

There is no doubt the company actually sent the spam.  
The 'smoking gun' is that their website recognized the email address for
an 'unsubscribe' from their mailings.

The people that 'need to know' about the 'error of their ways' are the
include:
  John R Stephenson   President & CEO
  Ada Popkey  Finance director

And their
  Head of Marketing
  Head of Public Relations  or Corporate Communications.


___
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: USB Logitech QuickCam Ultra Vision (mic problem SOLVED)

[Da Rock]

On 03/06/12 11:46, sean wrote:

I just managed to get the mic working built into the camera.
I followed the Sound steps below that are included in pkg-message and 
that did the trick.
Hopefully these notes will help others having mic problems with the 
Logitech camera.


NOTE: Just before I followed the below steps I did recompile my kernel 
to include "snd_hda" support.

After I finished that task I did try Skype and it did not work.
I mention this just in case if someone is troubleshooting such a 
problem and "snd_hda" might be needed.


Thanks to all the helped,
Sean


2. Sound

Since the OSS interface was removed, Skype now uses linux-alsa compat 
packages.
By default you get one device corresponding to your default OSS dsp 
device (so
Skype will use it for ringing, incoming voice and mic). If that 
doesn't suit

needs, you can map the other dsp devices for example by editing
/compat/linux/etc/alsa/pcm/pcm-oss.conf. You need to (re)start Skype 
after you

edit this file in order to get Skype pick up the changes.
Adding the following to the stock file, and then starting Skype and 
choosing

in Options-->Sound Devices:   Speakers: oss1
will let you use the second dsp (usually the front panel connectors 
for your
headphones, while still hearing the call ringing and other 
notification on the

first dsp device (presumably the one you connect your speakers to).
pcm.oss1 {
type oss
device /dev/dsp1
hint {
description "Open Sound System"
}
}

ctl.oss1 {
type oss
device /dev/mixer1
hint {
description "Open Sound System"
}
}

Alsa was the death of me in linux - a real PITA. That and selinux...

Such a hack to get anything with alsa to work; I thought even linux had 
given up on it?

___
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: USB Logitech QuickCam Ultra Vision (mic problem SOLVED)

[sean]

I just managed to get the mic working built into the camera.
I followed the Sound steps below that are included in pkg-message and 
that did the trick.
Hopefully these notes will help others having mic problems with the 
Logitech camera.


NOTE: Just before I followed the below steps I did recompile my kernel 
to include "snd_hda" support.

After I finished that task I did try Skype and it did not work.
I mention this just in case if someone is troubleshooting such a problem 
and "snd_hda" might be needed.


Thanks to all the helped,
Sean


2. Sound

Since the OSS interface was removed, Skype now uses linux-alsa compat 
packages.
By default you get one device corresponding to your default OSS dsp 
device (so

Skype will use it for ringing, incoming voice and mic). If that doesn't suit
needs, you can map the other dsp devices for example by editing
/compat/linux/etc/alsa/pcm/pcm-oss.conf. You need to (re)start Skype 
after you

edit this file in order to get Skype pick up the changes.
Adding the following to the stock file, and then starting Skype and choosing
in Options-->Sound Devices:   Speakers: oss1
will let you use the second dsp (usually the front panel connectors for your
headphones, while still hearing the call ringing and other notification 
on the

first dsp device (presumably the one you connect your speakers to).
pcm.oss1 {
type oss
device /dev/dsp1
hint {
description "Open Sound System"
}
}

ctl.oss1 {
type oss
device /dev/mixer1
hint {
description "Open Sound System"
}
}


___
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"

Equine Vaccines offered by Santa Cruz

[Santa Cruz Biotechnology]

  Are you having trouble viewing this e-mail? [1]Click here to view it
  from our website.
  To ensure that you continue receiving emails from us, please add
  [2]santacruzbiotechnol...@scbt.com to your e-mail address book.


  [3][USEMAP:email.jpg]

Copyright © 2012 Santa Cruz Biotechnology, Inc. Santa Cruz
   Biotechnology, Inc. and the Santa Cruz Biotechnology, Inc. logo are
   registered trademarks of Santa Cruz Biotechnology, Inc. All content
contained in this website is property of Santa Cruz Biotechnology,
   Inc.
   and may be used only with the expressed written permission of Santa
  Cruz Biotechnology, Inc. All rights reserved.
Santa Cruz Biotechnology, Inc. is located at 2145 Delaware Avenue,
 Santa Cruz, CA 95060 USA
   Email: [4]webmas...@scbt.com

  If you desire to not receive our e-mail bulletins at
  freebsd-questions@freebsd.org, simply [5]unsubscribe or forward this
  email message to webmas...@scbt.com.
   Santa Cruz Biotechnology, Inc.

References

  1. 
http://www.scbt.com/emails/redirect.php?lang=en&promo=vaccines_20120305&date=03/05/2012&url=ah_promo.html
  2. mailto:santacruzbiotechnol...@scbt.com
  3. LYNXIMGMAP:file://localhost/tmp/tmpLBxZQ2.html#cattle
  4. mailto:webmas...@scbt.com
  5. http://www.scbt.com/email_bulletin.php?eid=freebsd-questions@freebsd.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: sysinstall

[Da Rock]

On 03/06/12 05:23, David Walker wrote:

Nikola Pavlović nzp at riseup.net

OK, here goes: (in Nelson Muntz's voice) Haha, you clown, that's what
you get for believing what documentation says.  Use a magnetized needle
and a steady hand you buffoon!
There.  I respect! :)

Well played.

It's a serious issue for me after 15 years of Windows on the desktop
to change environment to FreeBSD.
I've reached this point after lengthy deliberation with the intent to
change once only.

While I consider it disappointing and surprising that man pages are
suspect (no doubt most are accurate) the bottom line is the community
response which includes man page writers and you and me.
Well played there too.

Disregarding any hiccups, I'm running FreeBSD on my main machine, I've
installed X11 and Gnome and it works better than I could have
envisoned - the first video I went to on YouTube played ... roll on
HTML5 ... sound works ...

Fix my tv card and I'll shut up. :]

What tv card? Mine work fine
___
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"

Part-time Positions Available

[Ben Rolland Fisheries Co Ltd]

   INTERNATIONAL COMPANY SEEKS FOR REPRESENTATIVE IN TAIWAN
  
Part-time Positions Available.
  The job is based on administrative/customer service support.
  Immediate need for customer service representative seeking fun working
  environment, opportunity for advancement and hands on training provided.
  Will be responsible for supporting sales team, and resolving customer
  related issues for consumer product/services company.
  Great benefits. No money required (we are serious company located in United
  Kingdom,we will never ask our representatives any money in prior).
   Salary:
 - 6000 USD monthly income/part-time job
  Benefits:
  - No relocation required
  - Comprehensive life insurance
  - Professional, fun and highly motivated work environment
  - Outstanding benefits/compensation for full-time, permanent associates
  - Competitive base pay
  - TAX refund and all travel fees are repaid
  Please, contact our HR department at benrollan...@hotmail.co.uk if you are
  interested.
 
  With best regards,
  Ben Rolland.


___
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.4.rc6 (32bit Wine for 64bit FreeBSD)

[Mehmet Erol Sanliturk]

On Mon, Mar 5, 2012 at 3:00 PM, David Naylor wrote:

> On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote:
> > On Mon, Mar 5, 2012 at 6:55 AM, David Naylor
> wrote:
> > > Please include the full error message, also could you please try
> running
> > > those apps in a clean wine prefix.
> >
> > # pwd
> > /root/APPLY/PROGRAMS
> >
> > # wine x.exe
> >
> > err : module : LdrInitializeThunk Main exe initialization for
> > L"F:\\APPLY\\PROGRAMS\\x.exe" failed , status c017
>
> I have tried to reproduce the error on my side but was unable to.  The
> programs that I tested work without error.
>
>
This means that there are additional parts in your system which they do not
exist here .
Such parts are not added by "pkg_add wine-fbsd64 ..." .
I do not have any idea about which parts may be missing .



> I was expecting more output from wine...  Please see below about using a
> clean
> wine prefix.  Do you use the nvidia graphics driver?  If so please run (as
> root), and provide the output:
> # sh /usr/local/share/wine/patch-nvidia.sh
>
>

There is NO nvidia grphics driver . It is Intel DG965WH main board with its
integrated graphics driver .



> If nothing fixes your problem then please submit a bug report at
> bugs.winehq.org.
>
>
> > I could not understand the phrase :
> >
> > "in a clean wine prefix" .
>
> To run a program in a clean wine prefix do:
> env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe
>

This is NOT changing the error message . Only drive become Z: .



>
> You may need to use winetricks to install some support programs.
>
> Good luck
>


"winetricks" could NOT be found .



I tried wine which is added by

pkg_add -r wine

from packages

in FreeBSD 9.0 RELEASE i386 as it is installed .


On the same programs , the message is the same with amd64 message .



Thank you very much .

Mehmet Erol Sanliturk
___
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.4.rc6 (32bit Wine for 64bit FreeBSD)

[David Naylor]

On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote:
> On Mon, Mar 5, 2012 at 6:55 AM, David Naylor 
wrote:
> > Please include the full error message, also could you please try running
> > those apps in a clean wine prefix.
> 
> # pwd
> /root/APPLY/PROGRAMS
> 
> # wine x.exe
> 
> err : module : LdrInitializeThunk Main exe initialization for
> L"F:\\APPLY\\PROGRAMS\\x.exe" failed , status c017

I have tried to reproduce the error on my side but was unable to.  The 
programs that I tested work without error.  

I was expecting more output from wine...  Please see below about using a clean 
wine prefix.  Do you use the nvidia graphics driver?  If so please run (as 
root), and provide the output:
# sh /usr/local/share/wine/patch-nvidia.sh

If nothing fixes your problem then please submit a bug report at 
bugs.winehq.org.  


> I could not understand the phrase :
> 
> "in a clean wine prefix" .

To run a program in a clean wine prefix do:
env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe

You may need to use winetricks to install some support programs.  

Good luck


signature.asc
Description: This is a digitally signed message part.

Re: port to package amd64 to i386

[Chris Whitehouse]

On 05/03/2012 16:53, Matthew Seaman wrote:

On 05/03/2012 16:42, Bernt Hansson wrote:


Thank you for the pointer. I do find it a bit overkill to setup jails
and such, just to build a few ports. I was thinking more along the line of;

cd /usr/ports/"random port"

make "it for i386 even if we are building it on amd64, ooh by the way
build it as a package, and all dependencies as packages as well"




About the only way to cross-build ports is to set up a 32-bit jail on a
64-bit host.  I believe that is do-able, but I could be delusional.


Could you do it in a tinderbox? This thread

http://www.marcuscom.com/pipermail/tinderbox-list/2011-June/002177.html

discusses it a bit with a possible solution. Things have probably moved 
on since then which may or may not help.


Chris

___
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: sysinstall

[David Walker]

Nikola Pavlović nzp at riseup.net
> OK, here goes: (in Nelson Muntz's voice) Haha, you clown, that's what
> you get for believing what documentation says.  Use a magnetized needle
> and a steady hand you buffoon!

> There.  I respect! :)

Well played.

It's a serious issue for me after 15 years of Windows on the desktop
to change environment to FreeBSD.
I've reached this point after lengthy deliberation with the intent to
change once only.

While I consider it disappointing and surprising that man pages are
suspect (no doubt most are accurate) the bottom line is the community
response which includes man page writers and you and me.
Well played there too.

Disregarding any hiccups, I'm running FreeBSD on my main machine, I've
installed X11 and Gnome and it works better than I could have
envisoned - the first video I went to on YouTube played ... roll on
HTML5 ... sound works ...

Fix my tv card and I'll shut up. :]

Best wishes.
___
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: port to package amd64 to i386

[Polytropon]

On Mon, 05 Mar 2012 17:42:58 +0100, Bernt Hansson wrote:
> Thank you for the pointer. I do find it a bit overkill to setup jails 
> and such, just to build a few ports.

The "problem" here is that a specific build environment
is required.



> I was thinking more along the line of;
> 
> cd /usr/ports/"random port"
> 
> make "it for i386 even if we are building it on amd64, ooh by the way 
> build it as a package, and all dependencies as packages as well"

Again, a "problem" is that packages can only be generated
if the port has been installed, which is the "make package"
task typically following "make install", resulting in the
desired package in the /usr/ports/packages/ subtree. See
"man ports" regarding the "package" target. I think that
_could_ be overridden by specifying a different, "temporary"
$PREFIX to install to, but I haven't tested this approach.

For the dependencies, I think there was a setting to be
included in /etc/make.conf... MAKE_DEPENDS=PACKAGE? Something
like this will cause all dependencies to be built and
archived as a package.



> Oh man, man ports. But I do not find the flag 
> -build-for-another-system-cpu-whatever

Some settings can be transferred to the make environment,
usually /etc/make.conf is used.



> Can the ports system be (ab)used in that way?

I don't think it is that easy. :-(


-- 
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: port to package amd64 to i386

[Matthew Seaman]

On 05/03/2012 16:42, Bernt Hansson wrote:
> 
> Thank you for the pointer. I do find it a bit overkill to setup jails
> and such, just to build a few ports. I was thinking more along the line of;
> 
> cd /usr/ports/"random port"
> 
> make "it for i386 even if we are building it on amd64, ooh by the way
> build it as a package, and all dependencies as packages as well"
> 
> Oh man, man ports. But I do not find the flag
> -build-for-another-system-cpu-whatever
> 
> Can the ports system be (ab)used in that way?

In general, no.  There may be some ports that you could cross-compile,
but that depends on the upstream software having support for cross
compilation (basically allowing "--target foo" into the compilation
flags.) Even if you fix that you're going to run into difficulties as
soon as you try and compile a port that depends on shared libraries from
another port.  I don't think there's any mechanism for installing 32-bit
shlibs into ${LOCALBASE}/lib32 from packages.

Oh, and making packages is potentially a mine field, as you need to
install the port in order to package it.

About the only way to cross-build ports is to set up a 32-bit jail on a
64-bit host.  I believe that is do-able, but I could be delusional.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: port to package amd64 to i386

[Bernt Hansson]

2012-03-05 10:20, Edward M. skrev:

On 03/05/2012 12:42 AM, Bernt Hansson wrote:

Build the port on amd64 and install it on i386 as a package.

Is it possible? Pointers? Handholding? How-to?



http://filipenf.wordpress.com/2011/10/18/cross-compiling-for-x86-in-freebsd-64-bit/


Thank you for the pointer. I do find it a bit overkill to setup jails 
and such, just to build a few ports. I was thinking more along the line of;


cd /usr/ports/"random port"

make "it for i386 even if we are building it on amd64, ooh by the way 
build it as a package, and all dependencies as packages as well"


Oh man, man ports. But I do not find the flag 
-build-for-another-system-cpu-whatever


Can the ports system be (ab)used in that way?
___
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: semi OT: correct CIDR block?

[Tim Kellers]

On 03/05/12 09:30, Robert Huff wrote:

With my brain still on EBADSLEEP, I cannot decide if:

10.0.0.32-10.0.0.63

is correctly described by:

10.0.0.32/27

Anyone?  Please?


Robert Huff

___
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"


   Network = 10.0.0.32
Usable IPs = 10.0.0.33 to 10.0.0.62 for 30
 Broadcast = 10.0.0.63
   Netmask = 255.255.255.224
Wildcard Mask = 0.0.0.31



Looks pretty good to me.

Tim Kellers

___
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: semi OT: correct CIDR block?

[Duane Hill]

On Monday, March 05, 2012 at 14:30:01 UTC, roberth...@rcn.com confabulated:


> With my brain still on EBADSLEEP, I cannot decide if:

> 10.0.0.32-10.0.0.63

> is correctly described by:

> 10.0.0.32/27

> Anyone?  Please?

I use the online IP calculator all the time:

http://jodies.de/ipcalc?host=10.0.0.32&mask1=27&mask2=

-- 
If at first you don't succeed...
...so much for skydiving.

___
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: semi OT: correct CIDR block?

[Chris Knipe]

Yes.

cknipe@amnesiac ~ $ ipcalc 10.0.0.32/27
Address:   10.0.0.321010...001 0
Netmask:   255.255.255.224 = 27 ...111 0
Wildcard:  0.0.0.31 ...000 1
=>
Network:   10.0.0.32/27 1010...001 0
HostMin:   10.0.0.331010...001 1
HostMax:   10.0.0.621010...001 0
Broadcast: 10.0.0.631010...001 1
Hosts/Net: 30Class A, Private Internet



On Mon, Mar 5, 2012 at 4:30 PM, Robert Huff  wrote:
>
>        With my brain still on EBADSLEEP, I cannot decide if:
>
>        10.0.0.32-10.0.0.63
>
>        is correctly described by:
>
>        10.0.0.32/27
>
>        Anyone?  Please?
>
>
>                                Robert Huff
>
> ___
> 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"



-- 

Regards,
Chris Knipe
___
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: semi OT: correct CIDR block?

[Paul Macdonald]

On 05/03/2012 14:30, Robert Huff wrote:

With my brain still on EBADSLEEP, I cannot decide if:

10.0.0.32-10.0.0.63

is correctly described by:

10.0.0.32/27

Anyone?  Please?


Robert Huff

i cheated a bit but looks good
http://jodies.de/ipcalc?host=10.0.0.32&mask1=27&mask2=


___
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"



--
-
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-
t: 0131 5548070
m: 07970339546

Re: semi OT: correct CIDR block?

[Dimitri Yioulos]

On Monday 05 March 2012 9:30:01 am Robert Huff wrote:
>   With my brain still on EBADSLEEP, I cannot decide if:
>
>   10.0.0.32-10.0.0.63
>
>   is correctly described by:
>
>   10.0.0.32/27
>
>   Anyone?  Please?
>
>
>   Robert Huff
>
> ___
> 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"


Robert,

Sent to you directly, as I can't get to the fbsd list.

Your CIDR is correct.

Best,

Dimitri

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: semi OT: correct CIDR block?

[Julien Cigar]

jcigar@dev ~ % ipcalc 10.0.0.32-10.0.0.63
deaggregate 10.0.0.32 - 10.0.0.63
10.0.0.32/27

(net-mgmt/ipcalc)

On 03/05/2012 15:30, Robert Huff wrote:

With my brain still on EBADSLEEP, I cannot decide if:

10.0.0.32-10.0.0.63

is correctly described by:

10.0.0.32/27

Anyone?  Please?


Robert Huff

___
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"



--
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.

___
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: semi OT: correct CIDR block?

[Dimitri Yioulos]

On Monday 05 March 2012 9:30:01 am Robert Huff wrote:
>   With my brain still on EBADSLEEP, I cannot decide if:
>
>   10.0.0.32-10.0.0.63
>
>   is correctly described by:
>
>   10.0.0.32/27
>
>   Anyone?  Please?
>
>
>   Robert Huff
>
> ___
> 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"


Correct.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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"

semi OT: correct CIDR block?

[Robert Huff]

With my brain still on EBADSLEEP, I cannot decide if:

10.0.0.32-10.0.0.63

is correctly described by:

10.0.0.32/27

Anyone?  Please?


Robert Huff

___
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: PC-BSD on top of FreeBSD - does it matter ?

[Matthew Seaman]

On 05/03/2012 12:10, Jerry wrote:
> Matthew, is this the URL for iXsystems 
> that you are referring to?

Yep.  That's the company.

> I was examining their company page:
>  and they seem quite
> impressive. Also, the support page URL for PC-BSD:
>  is now apparently working.

Ah -- no.  The page I was referring to is:

http://www.ixsystems.com/ix/support/software/pc-bsd-support

which is still 404.  It's linked to from here:

http://www.pcbsd.org/index.php?option=com_zoo&task=category&category_id=85&Itemid=62

(bottom of that page)

and also also from the PC-PSD pulldown in the menubar at the top of the
front page of the site.  I did report this through their website, but
it's early yet in California, so they won't have had a chance to fix it yet.

> Obviously, the above is based on the belief that I am referring to the
> correct entity to begin with.

Right company, wrong web page.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

[Mehmet Erol Sanliturk]

On Mon, Mar 5, 2012 at 6:55 AM, David Naylor wrote:

> On 5 March 2012 13:41, Mehmet Erol Sanliturk 
> wrote:
> > On Sun, Mar 4, 2012 at 2:16 PM, David Naylor 
> > wrote:
> >>
> >> Hi,
> >>
> >> Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire
> [2].
> >>
> >> 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 [3] 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 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) =
> >> 91bc2288130c25704c9f1ac9d2923a6a
> >>  MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) =
> >> a57b6fed2401375562931f3516e1d50b
> >> [2] http://www.mediafire.com/wine_fbsd64
> >> [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh
> >
> >
> >
> > For any x.exe :
> >
> > wine x.exe
> >
> > is generating the following error :
> >
> > err: module : LdrInitializeThunk Main exe initialization for L"F:\\ ...
> path
> > ... \\x.exe" failed ,
> > status c017
>
> Please include the full error message, also could you please try running
> those apps in a clean wine prefix.
>


# pwd
/root/APPLY/PROGRAMS


# ls -l

-rw-r--r-- 1 root wheel 5491200 Feb 17 22:27 x.exe

# wine x.exe

err : module : LdrInitializeThunk Main exe initialization for
L"F:\\APPLY\\PROGRAMS\\x.exe" failed , status c017

--

The whole message is listed above .
Desktop environment is KDE4 .
Execution is attempted in Konsole Terminal .
In GNOME Terminal in KDE4 , the error message is the same .

I could not understand the phrase :


"in a clean wine prefix" .

-


>
> > where x.exe is in the current directory ( path is correct )
> >
> > in FreeBSD 9.0-RELEASE #0 ... GENERIC amd64
>
> I will try reproduce this when I get $HOME.
>
> Regards
>


Thank you very much .

Mehmet Erol Sanliturk
___
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: PC-BSD on top of FreeBSD - does it matter ?

[Jerry]

On Mon, 05 Mar 2012 09:52:15 +
Matthew Seaman articulated:

> On 04/03/2012 22:56, Da Rock wrote:
> >> That's also an obligation to test it.
> >> PC-BSD is a product, by a private company. The burden of proof is
> >> on them.
> 
> > PC-BSD is an organisation or group; I wouldn't go as far as calling
> > them a private company.
> 
> No, the company behind PC-BSD is called iXsystems.  They do an awful
> lot in the FreeBSD sphere, and PC-BSD is one of their products.  While
> PC-BSD is a community driven project, iXsystems employs the project
> founder and lead developer specifically to work on PC-BSD.  Click on
> the 'Professional PC-BSD Support' link of the PC-BSD menu on the
> pcbsd.org site, and you will see who it is that provides the paid-for
> support.
> 
> Hmmm... actually they might want to look at that, as it returns a 404
> page.

Matthew, is this the URL for iXsystems 
that you are referring to?

I was examining their company page:
 and they seem quite
impressive. Also, the support page URL for PC-BSD:
 is now apparently working.

Obviously, the above is based on the belief that I am referring to the
correct entity to begin with.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__


signature.asc
Description: PGP signature

nsswitch and unavailable backends

[Eugene M. Zheganin]

Hi.

I'm trying to set up LDAP user authentication. I use bet/nss_ldap and 
security/pam_ldap ports to do this.
I'm doing this following the article from the documentation set. Though 
it's not that complete and misses some very important stuff, I've 
actually set up the LDAP installations and my users are able to 
successfully authenticate and log in on my servers.


Then I ran into some serious issue. :) When the LDAP server if 
off/unavailable, users cannot log in - I mean, even the local users.


nsswitch.conf:

group: files ldap
hosts: files dns
networks: files
passwd: files ldap
shells: files
services: files
protocols: files
rpc: files

If I remove ldap - all is fine, of course, besides the fact that this 
breaks the LDAP authentication.
I've read the nsswitch manual and saw that I can handle the unavailable 
LDAP server with some action flags, but the default action is 'continue' 
already. I also tried the [notfound=return unavail=return 
tryagain=return] mantra (it's harmless to try since it's the last 
backup) but this didn't work either.


sshd crashes with signal 11, crond does the same. Sad.

On a machine running LDAP server the situation is even funnier: the LDAP 
server, even having a local account to work under, still tries to query 
himself on start, making the startup impossible.


Can this situation be solved ?
Right now I remove 'ldap' backend, start the slapd, add ldap backends 
again and so on.


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: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

[David Naylor]

On 5 March 2012 13:41, Mehmet Erol Sanliturk  wrote:
> On Sun, Mar 4, 2012 at 2:16 PM, David Naylor 
> wrote:
>>
>> Hi,
>>
>> Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire [2].
>>
>> 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 [3] 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 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) =
>> 91bc2288130c25704c9f1ac9d2923a6a
>>  MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) =
>> a57b6fed2401375562931f3516e1d50b
>> [2] http://www.mediafire.com/wine_fbsd64
>> [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh
>
>
>
> For any x.exe :
>
> wine x.exe
>
> is generating the following error :
>
> err: module : LdrInitializeThunk Main exe initialization for L"F:\\ ... path
> ... \\x.exe" failed ,
> status c017

Please include the full error message, also could you please try running
those apps in a clean wine prefix.

> where x.exe is in the current directory ( path is correct )
>
> in FreeBSD 9.0-RELEASE #0 ... GENERIC amd64

I will try reproduce this when I get $HOME.

Regards
___
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.4.rc6 (32bit Wine for 64bit FreeBSD)

[Mehmet Erol Sanliturk]

On Sun, Mar 4, 2012 at 2:16 PM, David Naylor wrote:

> Hi,
>
> Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire [2].
>
> 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 [3] 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 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) =
> 91bc2288130c25704c9f1ac9d2923a6a
>  MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) =
> a57b6fed2401375562931f3516e1d50b
> [2] http://www.mediafire.com/wine_fbsd64
> [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh
>


For any x.exe :

wine x.exe

is generating the following error :

err: module : LdrInitializeThunk Main exe initialization for L"F:\\ ...
path ... \\x.exe" failed ,
status c017

where x.exe is in the current directory ( path is correct )

in FreeBSD 9.0-RELEASE #0 ... GENERIC amd64


Thank you very much .


Mehmet Erol Sanliturk
___
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: PC-BSD on top of FreeBSD - does it matter ?

[Da Rock]

On 03/05/12 19:52, Matthew Seaman wrote:

On 04/03/2012 22:56, Da Rock wrote:

That's also an obligation to test it.
PC-BSD is a product, by a private company. The burden of proof is on
them.

PC-BSD is an organisation or group; I wouldn't go as far as calling them
a private company.

No, the company behind PC-BSD is called iXsystems.  They do an awful lot
in the FreeBSD sphere, and PC-BSD is one of their products.  While
PC-BSD is a community driven project, iXsystems employs the project
founder and lead developer specifically to work on PC-BSD.  Click on the
'Professional PC-BSD Support' link of the PC-BSD menu on the pcbsd.org
site, and you will see who it is that provides the paid-for support.
Yes, but that is sponsorship. That doesn't make it a company. They don't 
own it.


Unlike Oracle with MySQL, Java, and VBox... Or Citrix and Xen...
___
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: on purpose or forgotten ? hardcoded compiler in basesystem-makefiles

[Matthew Seaman]

On 05/03/2012 10:12, Dr. A. Haakh wrote:
> a quick search revealed following usages:

Some of the instances you've found are legitimate, some are in upstream
code in contributed software -- the FreeBSD build process may not even
use the Makefiles concerned.  But, yes on the whole, I think you're on
to something that needs fixing here.

> FreeBSD abaton.Haakh.de 9.0-STABLE FreeBSD 9.0-STABLE #0: Wed Feb 29
> 13:49:36 CET 2012 t...@abaton.haakh.de:/usr/obj/usr/src/sys/ABATON 
> i386
> 
> ah@abaton:~$ find /usr/src/ -name Makefile\* -exec egrep
> '^[[:blank:]]+[gc+]{2,3}[[:blank:]]+..' {} \; -print

[...]

> /usr/src/usr.bin/make/Makefile.dist
> gcc -M $(CFLAGS) $(SRC) >> Makefile.tmp

Although it doesn't seem to appear in the clang(1) man page, clang
supports the -M flag:

lucid-nonsense:/tmp:# clang -M hello.c
hello.o: hello.c /usr/include/stdio.h /usr/include/sys/cdefs.h \
  /usr/include/sys/_null.h /usr/include/sys/_types.h \
  /usr/include/machine/_types.h

No need for this sort of construct to be gcc specific.

> /usr/src/tools/test/dtrace/Makefile
> c++ -o $@ $< -lpthread

Not sure about this -- the intent may be to test the default system
compiler -- as of this last weekend you can install clang(1) as
/usr/bin/cc in stable/9, so this isn't necessarily gcc specific.

> /usr/src/tools/regression/pthread/unwind/Makefile
> gcc -c -o elftls.o ${.CURDIR}/elftls.S
> gcc -c -o tls-test.o ${.CURDIR}/tls-test-lib.c
> gcc $(CFLAGS) -rdynamic -o ttls3 ${.CURDIR}/tls-test.c

Whereas this looks like an oversight to me.

> /usr/src/crypto/openssl/demos/engines/ibmca/Makefile
> cc -I../../include divtest.c -o divtest ../../libcrypto.a
> cc -g -I../../include bnbug.c -o bnbug ../../libcrypto.a
> gcc -I../../include -g2 -ggdb -o exptest exptest.c ../../libcrypto.a
> gcc -I.. -g div.c ../../libcrypto.a

/usr/src/crypto holds raw sources imported from upstream; hard-coded
compiler names here is a problem the openssl project should address.

> /usr/src/contrib/ncurses/Makefile.os2
> g++ -c $(ALL_CFLAGS) $(ALL_CPPFLAGS) $< $(OUTPUT_OPTION)
> g++ -o $@ paranoia.o real.o $(LIBIBERTY)

Ditto /usr/src/contrib -- raw upstream sources.

> /usr/src/contrib/gcc/Makefile.in
> gcc -o asyncwatch asyncwatch.c ${CFLAGS}
> gcc -o devinfo devinfo.c ${CFLAGS}
> gcc -o device_list device_list.c  ${CFLAGS}
> gcc -o rc_pingpong rc_pingpong.c pingpong.c ${CFLAGS}
> gcc -o srq_pingpong srq_pingpong.c pingpong.c ${CFLAGS}

... although gcc being hardwired in the gcc sources is probably
intentional and quite legitimate.

I suggest that you repost your question on freebsd-hack...@freebsd.org,
as that will bring it to the attention of the people both interested in
and capable of addressing this sort of problem.  Submitting a PR
wouldn't go amiss either.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: PC-BSD on top of FreeBSD - does it matter ?

[Jerry]

On Mon, 05 Mar 2012 09:52:15 +
Matthew Seaman articulated:

> No, the company behind PC-BSD is called iXsystems.  They do an awful
> lot in the FreeBSD sphere, and PC-BSD is one of their products.  While
> PC-BSD is a community driven project, iXsystems employs the project
> founder and lead developer specifically to work on PC-BSD.  Click on
> the 'Professional PC-BSD Support' link of the PC-BSD menu on the
> pcbsd.org site, and you will see who it is that provides the paid-for
> support.
> 
> Hmmm... actually they might want to look at that, as it returns a 404
> page.

Nothing instills confidence in a potential client like a broken
"Support" page with the possible exception of calling a telephone
number and finding it has been disconnected.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

___
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"

on purpose or forgotten ? hardcoded compiler in basesystem-makefiles

[Dr. A. Haakh]

a quick search revealed following usages:

FreeBSD abaton.Haakh.de 9.0-STABLE FreeBSD 9.0-STABLE #0: Wed Feb 29 
13:49:36 CET 2012 t...@abaton.haakh.de:/usr/obj/usr/src/sys/ABATON  i386


ah@abaton:~$ find /usr/src/ -name Makefile\* -exec egrep 
'^[[:blank:]]+[gc+]{2,3}[[:blank:]]+..' {} \; -print
cc -D__dead2="" -D__unused="" -Darc4random=random 
-D__FBSDID="static const char *id=" -DDEFSHELLNAME=\"sh\" -I. -c *.c

cc *.o -o pmake
/usr/src/usr.bin/make/Makefile.dist
gcc -M $(CFLAGS) $(SRC) >> Makefile.tmp
/usr/src/crypto/openssl/demos/engines/cluster_labs/Makefile
gcc -M $(CFLAGS) $(SRC) >> Makefile.tmp
/usr/src/crypto/openssl/demos/engines/zencod/Makefile
gcc -M $(CFLAGS) $(SRC) >> Makefile.tmp
/usr/src/crypto/openssl/demos/engines/ibmca/Makefile
cc -I../../include divtest.c -o divtest ../../libcrypto.a
cc -g -I../../include bnbug.c -o bnbug ../../libcrypto.a
gcc -I../../include -g2 -ggdb -o exptest exptest.c ../../libcrypto.a
gcc -I.. -g div.c ../../libcrypto.a
/usr/src/crypto/openssl/crypto/bn/Makefile
cc -g -I../../include -c test.c
cc -g -I../../include -o test test.o -L../.. -lcrypto
cc -g -I../../include -c pk.c
cc -g -I../../include -o pk pk.o -L../.. -lcrypto
/usr/src/crypto/openssl/crypto/asn1/Makefile
gcc -o ${.TARGET} ${_f} -lrt
/usr/src/tools/test/dtrace/Makefile
c++ -o $@ $< -lpthread
/usr/src/tools/regression/pthread/unwind/Makefile
gcc -c -o elftls.o ${.CURDIR}/elftls.S
gcc -c -o tls-test.o ${.CURDIR}/tls-test-lib.c
gcc $(CFLAGS) -rdynamic -o ttls3 ${.CURDIR}/tls-test.c
/usr/src/tools/regression/tls/ttls3/Makefile
gcc -Wall -o accf_data_attach accf_data_attach.c
/usr/src/tools/regression/sockets/accf_data_attach/Makefile
gcc $(LDFLAGS) $(DLL_LN_OPTS) ./lib/$*$(DLL_TAG).lib \
gcc $(LDFLAGS) $(DLL_LN_OPTS) ./lib/$*$(DLL_TAG).lib \
/usr/src/contrib/ncurses/Makefile.os2
g++ -c $(ALL_CFLAGS) $(ALL_CPPFLAGS) $< $(OUTPUT_OPTION)
g++ -o $@ paranoia.o real.o $(LIBIBERTY)
/usr/src/contrib/gcc/Makefile.in
gcc -o asyncwatch asyncwatch.c ${CFLAGS}
gcc -o devinfo devinfo.c ${CFLAGS}
gcc -o device_list device_list.c  ${CFLAGS}
gcc -o rc_pingpong rc_pingpong.c pingpong.c ${CFLAGS}
gcc -o srq_pingpong srq_pingpong.c pingpong.c ${CFLAGS}
gcc -o uc_pingpong uc_pingpong.c pingpong.c ${CFLAGS}
gcc -o ud_pingpong ud_pingpong.c pingpong.c ${CFLAGS}
/usr/src/contrib/ofed/libibverbs/examples/Makefile
cc -E $$i |\
/usr/src/contrib/libreadline/examples/rlfe/Makefile.in
cc -o test ${.CURDIR}/test.c -lrpcsvc
/usr/src/usr.sbin/rpc.lockd/Makefile
cc -o test test.c -lrpcsvc
/usr/src/usr.sbin/rpc.statd/Makefile
gcc -g -DSPARC_XXX ${MUL} -o ${.TARGET}
gcc -g -DSPARC_XXX ${DIVREM} -o ${.TARGET}
/usr/src/lib/libc/quad/TESTS/Makefile
cc ${CFLAGS} -static tst01.o -o tst01 libdisk.a
/usr/src/lib/libdisk/Makefile
gcc -g3 msgring.lex.c msgring.yacc.c -o msgring
/usr/src/sys/mips/rmi/Makefile.msgring

ah@abaton:~$ find /usr/src/ -name Makefile\* -exec egrep 
'^[[:blank:]]+cpp[[:blank:]]+..' {} \; -print

cpp -DOVLY_IRQ_SAVE $(srcdir)/emultempl/spu_ovl.S spu_ovl.s
/usr/src/contrib/binutils/ld/Makefile.in
cpp -DOVLY_IRQ_SAVE $(srcdir)/emultempl/spu_ovl.S spu_ovl.s
/usr/src/contrib/binutils/ld/Makefile.am

___
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: PC-BSD on top of FreeBSD - does it matter ?

[Matthew Seaman]

On 04/03/2012 22:56, Da Rock wrote:
>> That's also an obligation to test it.
>> PC-BSD is a product, by a private company. The burden of proof is on
>> them.

> PC-BSD is an organisation or group; I wouldn't go as far as calling them
> a private company.

No, the company behind PC-BSD is called iXsystems.  They do an awful lot
in the FreeBSD sphere, and PC-BSD is one of their products.  While
PC-BSD is a community driven project, iXsystems employs the project
founder and lead developer specifically to work on PC-BSD.  Click on the
'Professional PC-BSD Support' link of the PC-BSD menu on the pcbsd.org
site, and you will see who it is that provides the paid-for support.

Hmmm... actually they might want to look at that, as it returns a 404 page.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: port to package amd64 to i386

[Edward M.]

On 03/05/2012 12:42 AM, Bernt Hansson wrote:

Build the port on amd64 and install it on i386 as a package.

Is it possible? Pointers? Handholding? How-to? 




http://filipenf.wordpress.com/2011/10/18/cross-compiling-for-x86-in-freebsd-64-bit/

___
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"

port to package amd64 to i386

[Bernt Hansson]

Hello list

I want to build packages from ports on AMD64 for use on i386
since the i386 system is;


pid 21629 (cc1plus), uid 0, was killed: out of swap space

When building firefox.

Added some swap as a file so it's building as I type.

Thinking that the AMD system I can access is a wee more powerfull
than the i386, I was thinking in the line of;

Build the port on amd64 and install it on i386 as a package.

Is it possible? Pointers? Handholding? How-to?

This is the i386;

FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011
r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2524.94-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf27  Family = f  Model = 2  Stepping 
= 7 
Features=0xbfebfbff

Features2=0x400
real memory  = 537395200 (512 MB)
avail memory = 498135040 (475 MB)


This is the amd64;

FreeBSD 8.2-STABLE #0: Thu Jan 12 15:13:06 CET 2012 
user@fqdn:/usr/home/user/disk8/obj/usr/home/user/disk8/src/sys/GENERIC amd64

Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) II X2 250 Processor (3013.63-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x100f63  Family = 10  Model = 6 
Stepping = 3


Features=0x178bfbff
Features2=0x802009
AMD 
Features=0xee500800
AMD 
Features2=0x37ff

TSC: P-state invariant
real memory  = 17179869184 (16384 MB)
avail memory = 16523640832 (15758 MB)
___
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"