Re: portupgrade stale dependencies

[Andrew P.]

On 10/27/05, John DeStefano <[EMAIL PROTECTED]> wrote:

<...snip...>

>
> After clearing out the ports, updating ports (with portsnap) and
> source, and rebuilding the system and kernel... it seemed the ultimate
> problem was actually a dependency of the package to apache1.3. After I
> ran 'pkgdb -F' and "fixed" this dependency to point to apache2.1, but
> I still had trouble installing ports.
>
> 'portsdb -Uu' would not run, so I ran 'make fetchindex' and
> 'portupdate -a'.  From what I've read, this _should_ create an index
> and update all out-of-date ports and their dependencies, but it never
> has worked for me.  I just tried this combination again, and it
> (again) punts during portupdate.  This time, 38 ports were skipped and
> 7 failed, the first failure being a strange compiler error in updating
> from apache-2.0.48.
>
> I've been fighting with ports for long enough now to have become a bit
> frustrated with them.  If you have any thoughts or suggestions on how
> to troubleshoot them, please pass them on.
>
> Thanks,
> ~John
>

Do not fix dependencies if you're not sure that they
are really broken. Don't use apache21 unless 2.0
is absolutely inappropriate. The proper way to change
dependencies from apache1 to apache2 is to add
"WITH_APACHE2=true" to /etc/make.conf (or to
/usr/local/etc/pkgtools.conf, but that's an advanced
topic).

If you have portsdb utility, don't use make fetchindex,
just add -F to portsdb: "portsdb -uUF" will work fine.

You cann add -k to portupgrade, so that it doesn't
skip ports (but it won't fix the failed ones).

John, you'll have to spend a few hours reading
ports documentation before you find them really
great (which they really are).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

finding the correct man page ???

[ke.han]

Hello list,
I am  working on configuring a new system and have run across maillist 
comments such as:


"The comment in GENERIC is not accurate, the bge driver supports 5721
based cards for a couple of month now (the manpage in RELENG_5 is correct)."

The problem is, which man page? There are so many man pages, I rarely 
know how to find what I'm looking for.  The whatis command does no good 
for this sort of search.  Since I'm still pretty new to things, is there 
some searching mechanism or naming structure I'm not clued into?


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

Re: math/grace port: "libXcursor.so.1.0" not found ?? [SOLVED]

[Rob]

--- Igor Robul <[EMAIL PROTECTED]> wrote:

> Rob wrote:
> 
> >
> >When I patch grace with this dummy dlerror(),
> >prior to the dl-function calls, all works like
> >a charm (and you don't need the link in
> >/usr/X11R6/lib anymore).
> >
> >As I said before, I now have to find out why
> >grace activates the dlerror() at start-up.
> >  
> >
> So, problem is on grace side, not on FreeBSD side.
> I think there are some differences in execution
> environment for grace on Linux and FreeBSD.

Then "we" have to tell the grace developper, who
is a devote Linux user, about the oddities on
FreeBSD, or "we" have to come up with a reasonable
patch to make it work properly on FreeBSD.

Meanwhile I digged a little deeper in the grace
source code, to find out at what place exactly
the dlerror() error-indicator is set. When
grace initializes its GUI, there is this kind
of code:

---
   XtAppContext app_con;
   Display *disp = NULL;
   char *display_name = NULL;

   XtSetLanguageProc(NULL, NULL, NULL); 
   XtToolkitInitialize();
   app_con = XtCreateApplicationContext();

   disp = XOpenDisplay(display_name);
---

(I have simplified this code snippet a bit, for
this example; also, grace uses Motif for its GUI).

Before the XOpenDisplay() call, dlerror() does
not have the error-indicator set, but after
that call, it has.

Is this where Linux and FreeBSD are out-of-sync?
Or does Grace something wrong here, or is this
a problem cause by FreeBSD or Xorg?

I feel I'm getting closer and closer, but still
I have not really a good idea of what's going on
here!

Thanks,
Rob.





__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Which version of FreeBSD a binary was compiled for?

[Andrew P.]

On 10/27/05, Joshua Tinnin <[EMAIL PROTECTED]> wrote:
> On Wed 26 Oct 05 09:18, "Andrew P." <[EMAIL PROTECTED]> wrote:
> > On 10/26/05, Robert Huff <[EMAIL PROTECTED]> wrote:
> > > Andrew P. writes:
> > > >  > file /usr/bin/man
> > > >  >
> > > >  > on my machine outputs:
> > > >  >
> > > >  > /usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version
> > > >  > 1 (FreeBSD), for FreeBSD 5.4-CURRENT (rev 3), dynamically
> > > >  > linked (uses shared libs), stripped
> > > >
> > > >  Oh, it's just that file hasn't leared anything about
> > > >  FreeBSD 6 yet, so it doesn't display version info
> > > >  when run against my binaries.
> > >
> > > Curious.
> > >
> > > huff@> file /usr/bin/man
> > > /usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1
> > > (FreeBSD), for FreeBSD 7.0 (73), dynamically linked (uses
> > > shared libs), stripped huff@>
> >
> > I tried both versions of file (base system and ports)
> > on 6.0 RC1, none showed any info about that
> > /usr/bin/man (or any other system binary I tried).
> >
> > On my firewall (5.4) it works.
>
> That's odd. Am on 6.0-RC1:
>
> # uname -a
> FreeBSD smogmonster.local 6.0-RC1 FreeBSD 6.0-RC1 #0: Thu Oct 20
> 14:41:23 MDT 2005
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL60  i386
>
> % file /usr/bin/xargs
> /usr/bin/xargs: ELF 32-bit LSB executable, Intel 80386, version 1
> (FreeBSD), for FreeBSD 6.0 (600034), dynamically linked (uses shared
> libs), stripped
>
> % file /usr/bin/man
> /usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1
> (FreeBSD), for FreeBSD 6.0 (600034), dynamically linked (uses shared
> libs), stripped
>
> % file /bin/echo
> /bin/echo: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),
> for FreeBSD 6.0 (600034), dynamically linked (uses shared libs),
> stripped
>
>
> I know I built valgrind just a few days ago:
>
> % file /usr/local/bin/valgrind
> /usr/local/bin/valgrind: ELF 32-bit LSB executable, Intel 80386, version
> 1 (FreeBSD), for FreeBSD 6.0 (600034), statically linked, stripped
>
> vim, too:
>
> % file /usr/local/bin/vim
> /usr/local/bin/vim: ELF 32-bit LSB executable, Intel 80386, version 1
> (FreeBSD), for FreeBSD 6.0 (600034), dynamically linked (uses shared
> libs), stripped
>
>
> I'm not sure what it means when this information isn't accessible, but
> I'd say it's symptomatic of another issue, and most likely it's not
> good. If you built from source, did you follow the procedure described
> in the handbook?
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
>
> Not sure, but are you installing kernel after building world, and then
> installing world in single user? I've seen strange things happen if you
> don't do this procedure the right way. Of course, I'm just guessing, as
> I'm not at all sure what could be causing this problem or what your
> exact circumstances are.
>
> - jt
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

sat64% uname -a
FreeBSD sat64.net17 6.0-RC1 FreeBSD 6.0-RC1 #2: Fri Oct 14 22:57:08 MSD 2005
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SATCUR32  i386

sat64% file /usr/bin/xargs
/usr/bin/xargs: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dyn
amically linked (uses shared libs), stripped

sat64% file /usr/bin/man
/usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynam
ically linked (uses shared libs), stripped

sat64% file /bin/echo
/bin/echo: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamica
lly linked (uses shared libs), stripped

sat64% file /usr/local/bin/waveplay
/usr/local/bin/waveplay: ELF 32-bit LSB executable, Intel 80386, version 1 (Free
BSD), dynamically linked (uses shared libs), stripped

sat64% file /usr/local/lib/oss/bin/ossplay
/usr/local/lib/oss/bin/ossplay: ELF 32-bit LSB executable, Intel 80386, version
1 (FreeBSD), dynamically linked (uses shared libs), stripped

sat64% /usr/local/bin/file /usr/local/lib/oss/bin/ossplay
/usr/local/lib/oss/bin/ossplay: ELF 32-bit LSB executable, Intel 80386, version
1 (FreeBSD), dynamically linked (uses shared libs), stripped


Maybe you're right. I never go to single-user when
upgrading. But then, I'm the only user and there are
not many processes. I'm not gonna worry anyway,
hope it's not a rootkit :-)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: finding the correct man page ???

[Andrew P.]

On 10/27/05, ke.han <[EMAIL PROTECTED]> wrote:
> Hello list,
> I am  working on configuring a new system and have run across maillist
> comments such as:
>
> "The comment in GENERIC is not accurate, the bge driver supports 5721
> based cards for a couple of month now (the manpage in RELENG_5 is correct)."
>
> The problem is, which man page? There are so many man pages, I rarely
> know how to find what I'm looking for.  The whatis command does no good
> for this sort of search.  Since I'm still pretty new to things, is there
> some searching mechanism or naming structure I'm not clued into?
>
> thanks, ke han
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

sat64% man -k 5721
bge(4)   - Broadcom BCM570x/5714/5721/
5750/5751/5789 PCI Gigabit Ethernet adapter driver
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: math/grace port: "libXcursor.so.1.0" not found ?? [SOLVED]

[Igor Robul]

Rob wrote:


---
  XtAppContext app_con;
  Display *disp = NULL;
  char *display_name = NULL;

  XtSetLanguageProc(NULL, NULL, NULL); 
  XtToolkitInitialize();

  app_con = XtCreateApplicationContext();

  disp = XOpenDisplay(display_name);
---

(I have simplified this code snippet a bit, for
this example; also, grace uses Motif for its GUI).

Before the XOpenDisplay() call, dlerror() does
not have the error-indicator set, but after
that call, it has.

Is this where Linux and FreeBSD are out-of-sync?
Or does Grace something wrong here, or is this
a problem cause by FreeBSD or Xorg?

 

I think, that when XOpenDisplay called, ld.so tries load some libraries 
from preconfigured paths, and

last unsuccessful attempt is recorded for dlerror().

dlopen() _does not_ reset dlerror() state on sucess, it just returns non 
NULL. So you must not check dlerror() for error condition, you need 
check return result of dlopen(), and if it is NULL, then you need use 
dlerror().


So, code in grace:

  dlopen("library name", MODE);
  if (dlerror() != NULL) {
 report_error();
 exit(1);


  }


need to be:

handle = dlopen("library name", MODE);
if (handle == NULL) {  
   report_error(dlerror());


 exit(1);

}

just because dlerror() != NULL is not indicator of error.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading from 5.3 to 6.0 (was: no subject)

[Andrew P.]

On 10/27/05, George Katsanos <[EMAIL PROTECTED]> wrote:
> Hello ,
>
>
> Since the actual 6.0 Release is taking too long , would you suggest me
> installing 6.0 RC-1 and then then 6.0 is out , can I just apply some patches
> , or I should Re-makeworld everything?...
>
> And another question , I'm on a PIII 550 with 256MB ram . I have 5.3 and
> some broken libs .Would you suggest me doing a fresh install , or a make
> world ? Consider I don't have the experience the second procedure takes ,
> but I've heard both opinions. Should I do a portupgrade -a after the
> makeworld ?...
>
>
> Thank you
>
> George
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

Yes, you can try 6.0RC1, it's pretty stable.

Read the Handbook and stick to the advice:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

You shouldn't have any trouble.

You should do "portupgrade -fa" (recompile all your
ports) after the upgrade is finished, but it's not an
urgent matter. You can as well wait a few weeks
and recompile them all then - thanks to binary
compatibility they will work until then.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: lost in nowhere land on 5.2.1

[Andrew P.]

On 10/27/05, Brian Howick <[EMAIL PROTECTED]> wrote:
> I set up a copy of 5.2.1 RELEASE a few years back and I am trying to upgrade
> it.
>
> The problem is I set it up over the net and not from a CD.. so when I try to
> upgrade I am told that whatever FTP server I connect to does not have the
> files...
>
> What can I do?
>
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>

cvsup and make world

If you run into trouble, try upgrading to 5.3 or 5.4 first and
than to 6.0.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: math/grace port: "libXcursor.so.1.0" not found ?? [SOLVED]

[Igor Robul]

Igor Robul wrote:

dlopen() _does not_ reset dlerror() state on sucess, it just returns 
non NULL. So you must not check dlerror() for error condition, you 
need check return result of dlopen(), and if it is NULL, then you need 
use dlerror().


So, code in grace:

  dlopen("library name", MODE);
  if (dlerror() != NULL) {
 report_error();
 exit(1);


Actual code in grace is:

newkey.data = dlsym(handle, dl_function);
   if ((error = (char *) dlerror()) != NULL) {
   errmsg(error);
   dlclose(handle);
   return RETURN_FAILURE;
   }

But I think it is needed to be something like (I dont know if they need 
"error" variable later):


newkey.data = dlsym(handle, dl_function);
   if (  newkey.data == NULL) {
   errmsg(error=dlerror());
   dlclose(handle);
   return RETURN_FAILURE;
   }


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

Re: math/grace port: "libXcursor.so.1.0" not found ?? [SOLVED]

[Igor Robul]

Sorry,
I have reread manual page for dlerror() and found that it need clear 
error state after call, but

dlerror() in src/libc/gen/dlfcn.c does not do this:

#pragma weak dlerror
const char *
dlerror(void)
{
   return sorry;
}

So error is in FreeBSD libc, if I understand this correctly. I'll do PR.

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

Re: math/grace port: "libXcursor.so.1.0" not found ?? [SOLVED]

[Igor Robul]

Igor Robul wrote:


Sorry,
I have reread manual page for dlerror() and found that it need clear 
error state after call, but

dlerror() in src/libc/gen/dlfcn.c does not do this:

#pragma weak dlerror
const char *
dlerror(void)
{
   return sorry;
}

So error is in FreeBSD libc, if I understand this correctly. I'll do PR.


Bad day for me :-(.

Above code is from src/libc/gen/dlfcn.c, but real dlerror for dynamicaly 
linked executables is in rtdl.c, and it works as described in  manual 
page (clears error status).


So problem is somewhere else. Sorry for false info.

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

Window Scaling

[ptitoliv]

Hello everybody,

I have got 2 dedicated servers located on the same network. 1 is running
on FreeBSD and the other under Linux Debian. The problem is that on the
BSD box, it is impossible to have a transfer rate higer than 200 kB/s with
one connection. If I create simultaneous connections, I can reach more
higher transfer rates.

On my Debian Box, I can reach easily 900 KB/s with only one connection. I
have heard about TCP Window size and Window scaling.

Do you think that it is possible to modify parameters on the BSD box in
order to reach the same transfer rates than the Debian box with only one
connection ?

Thank you for your answers.

Best Regards,
Ptitoliv

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

kqueue and polling ... are they related?

[ke.han]

Dear list,
I will be using kqueue on freeBSD 6.0-rc1 and need to understand the 
relationship between kqueue and polling since polling support requires 
explicite enabling and choosing the correct ethernet drivers, etc...
First, is there a relationship between kqueue and polling?  The kqueue 
man page refers to the poll man page.  The polling man page does not 
refer to either poll or kqueue.
So, does kqueue require polling to be enabled? Any elaboration would be 
appreciated.

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

Re: Maintaining my music collection (off topic)

[Parv]

in message <[EMAIL PROTECTED]>,
wrote Will Maier thusly...
>
> On Wed, Oct 26, 2005 at 06:39:48AM -0400, Parv wrote:
> > Looks like this script is not going to work in FreeBSD /bin/sh.
> > Install one of shells/bash* (guessing) ports and run this script
> > under that shell (unless somebody does the conversion for you).
> 
> FreeBSD sh (1) supports parameter expansion, including expansions used
> in the referenced function.

  (The deleted part Will M refereed above was similar to ${var%/*}.)

Yes, you are correct.  I misremembered and did not paid much
attention to sh(1) man page before firing off my earlier post.


  - Parv

-- 

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

Re: kqueue and polling ... are they related?

[Erik Trulsson]

On Thu, Oct 27, 2005 at 05:09:58PM +0800, ke.han wrote:
> Dear list,
> I will be using kqueue on freeBSD 6.0-rc1 and need to understand the 
> relationship between kqueue and polling since polling support requires 
> explicite enabling and choosing the correct ethernet drivers, etc...
> First, is there a relationship between kqueue and polling?  The kqueue 
> man page refers to the poll man page.  The polling man page does not 
> refer to either poll or kqueue.
> So, does kqueue require polling to be enabled? Any elaboration would be 
> appreciated.
> thanks, ke han

The kqueue(2) manpage does refer to the manpage for the poll(2) system call,
which is an older alternative to using kqueue. The same goes for select(2), 
which is also an alternative to using kqueue(2) or poll(2).

None of these have any relation to polling of the network interfaces as
described in the polling(4) manpage.  
The only connection between poll(2) and polling(4) is that they have similar
names.


So, to answer your question: No, you do not need to have polling enabled in
order to use kqueue.

-- 

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

Window Scaling

[ptitoliv]

Hello everybody,

I have got 2 dedicated servers located on the same network. 1 is running
on FreeBSD and the other under Linux Debian. The problem is that on the
BSD box, it is impossible to have a transfer rate higer than 200 kB/s with
one connection. If I create simultaneous connections, I can reach more
higher transfer rates.

On my Debian Box, I can reach easily 900 KB/s with only one connection. I
have heard about TCP Window size and Window scaling.

Do you think that it is possible to modify parameters on the BSD box in
order to reach the same transfer rates than the Debian box with only one
connection ?

Thank you for your answers.

Best Regards,
Ptitoliv


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

Re: math/grace port: "libXcursor.so.1.0" not found ?? [FBSD/Xorg error?]

[Rob]

--- Igor Robul <[EMAIL PROTECTED]> wrote:

> Rob wrote:
> 
> >---
> >   XtAppContext app_con;
> >   Display *disp = NULL;
> >   char *display_name = NULL;
> >
> >   XtSetLanguageProc(NULL, NULL, NULL); 
> >   XtToolkitInitialize();
> >   app_con = XtCreateApplicationContext();
> >
> >   disp = XOpenDisplay(display_name);
> >---
> >
> >(I have simplified this code snippet a bit, for
> >this example; also, grace uses Motif for its GUI).
> >
> >Before the XOpenDisplay() call, dlerror() does
> >not have the error-indicator set, but after
> >that call, it has.
> >
> >Is this where Linux and FreeBSD are out-of-sync?
> >Or does Grace something wrong here, or is this
> >a problem cause by FreeBSD or Xorg?
>
> I think, that when XOpenDisplay called, ld.so tries
> load some libraries 
> from preconfigured paths, and
> last unsuccessful attempt is recorded for dlerror().

Here is the two points response from the grace
mailinglist:


1. Because XOpenDisplay() causes dlerror() to be
   set:
   One of the FreeBSD X libraries is broken,
   calling an inexisting libXcursor.so.1.0.

2. The FreeBSD dynamic loader is broken, ignoring
   unresolved references in DLLs both at
   initialization and run time.


So is the libX11.so.6 on FreeBSD (or another) to be
blamed?

Or is something more fundamentally wrong with
FreeBSD?

Rob.




__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kqueue and polling ... are they related?

[ke.han]

None of these have any relation to polling of the network interfaces as
described in the polling(4) manpage.  
The only connection between poll(2) and polling(4) is that they have similar

names.


So, to answer your question: No, you do not need to have polling enabled in
order to use kqueue.



thanks for the quick response...

Since it appears that polling is meant to help out 
performance/scalability, would enabling polling in a system using kqueue 
possibly provide addition benefits than not use polling in a (SMP) 
system using kqueue??


Also, it appears that polling is just something that needs to be turned 
on.  i.e. the application does not need to make API calls to take 
advantage of polling.  Is this true??


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

FreeBSD 6.0-RC1/i386: build port java/eclipse fails: Error occurred during initialization of VM

[O. Hartmann]

Hello.

I got this error during compiling 'eclipse' from ports:

===>  Building for eclipse-3.1.1
Error occurred during initialization of VM
Could not reserve enough space for object heap
Assuming RHEL CLASSPATH compatible.
Error occurred during initialization of VM
Could not reserve enough space for object heap
Assuming RHEL CLASSPATH compatible.
Error occurred during initialization of VM
Could not reserve enough space for object heap
*** Error code 1

Target machine is a most recent build-world built FreeBSD 6.0-RC1 with 
1GB RAM (Dell Optiplex G280, dmesg follows). HTT is enabled. Box uses 
the i915G graphics with 8MB video memory.


The above shown error sounds like the lack of main memory ... But for 
the case of another issue, please help.


Thanks, Oliver


Copyright (c) 1992-2005 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.
FreeBSD 6.0-RC1 #80: Thu Oct 27 10:29:40 UTC 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/EDDA
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.60-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf41  Stepping = 1
  
Features=0xbfebfbff
  Features2=0x441d>
  AMD Features=0x10
  Hyperthreading: 2 logical CPUs
real memory  = 1063804928 (1014 MB)
avail memory = 1031860224 (984 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 8
ioapic0  irqs 0-23 on motherboard
lapic0: Forcing LINT1 to edge trigger
netsmb_dev: loaded
npx0: [FAST]
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
acpi0: Power Button (fixed)
pci_link0:  irq 11 on acpi0
pci_link1:  irq 10 on acpi0
pci_link2:  irq 10 on acpi0
pci_link3:  on acpi0
pci_link4:  irq 5 on acpi0
pci_link5:  irq 9 on acpi0
pci_link6:  irq 5 on acpi0
pci_link7:  irq 9 on acpi0
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0:  on acpi0
p4tcc0:  on cpu0
cpu1:  on acpi0
p4tcc1:  on cpu1
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  irq 16 at device 1.0 on pci0
pci1:  on pcib1
pci0:  at device 2.0 (no driver attached)
pci0:  at device 2.1 (no driver attached)
pcib2:  irq 16 at device 28.0 on pci0
pci2:  on pcib2
bge0:  mem 
0xdfcf-0xdfcf irq 16 at device 0.0 on pci2
miibus0:  on bge0
brgphy0:  on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto
bge0: Ethernet address: 00:11:43:aa:71:72
pcib3:  irq 17 at device 28.1 on pci0
pci3:  on pcib3
uhci0:  port 0xff80-0xff9f 
irq 21 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xff60-0xff7f 
irq 22 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xff40-0xff5f 
irq 18 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3:  port 0xff20-0xff3f 
irq 23 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3:  on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0:  mem 0xffa80800-0xffa80bff irq 21 at 
device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4:  on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
uhub5: vendor 0x0424 product 0xa700, class 9/0, rev 2.00/0.00, addr 2
uhub5: multiple transaction translators
uhub5: 4 ports with 4 removable, self powered
pcib4:  at device 30.0 on pci0
pci4:  on pcib4
pcm0:  port 0xec00-0xecff,0xe8c0-0xe8ff mem 
0xdfebfe00-0xdfeb,0xdfebfd00-0xdfebfdff irq 23 at device 30.2 on pci0
pcm0: [GIANT-LOCKED]
pcm0: 
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0
ata0:  on atapci0
ata1:  on atapci0
atapci1:  port 
0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf irq 20 at 
device 31.2 on pci0
atapci1: failed to enable memory mapping!
ata2:  on atapci1
ata3:  on atapci1
ichsmb0:  port 0xe8a0-0xe8bf irq 17 at device 31.3 on pci0
ichsmb0: [GIANT-LOCKED]
smbus0:  on ichsmb0
smb0:  on smbus0
fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  port 0x378-0x37f,0x778-0x77f irq 7 drq 1 on 
acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COM

Unable to upgrade kdenetwork using portupgrade

[Teo De Las Heras]

I'm running FreeBSD 5.4 on my dektop with X.org  and KDE 3.4.
I'm synchronizing my ports tree using cvsup.
 When I run the following command
 portupgrade -rR kdenetwork
 It fails because it is unable to upgrade the kdelibs. The error messages
says to run -F to force.
 What is the consequence?
 Would it be simpler to run portupgrade -rR kde?
 Thanks,
 Teo
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Product Ordering - Payment Methods and Overseas Postage

[bjrobilliard]

Dear Sir/Madam,

I was enquiring as to whether or not you sell official box sets.  Is so,
what are the contents of these sets?  Are they manufactured media or are
they just burnt CDs?  Who sells these?

Under which licence is FreeBSD released?  Where can a copy of this be located
on the web?

When will FreeBSD version 6.0 be released?

Yours faithfully,
Bryce Robilliard

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

Re: Product Ordering - Payment Methods and Overseas Postage

[eoghan]

[EMAIL PROTECTED] wrote:

Hi


Dear Sir/Madam,

I was enquiring as to whether or not you sell official box sets.  Is so,
what are the contents of these sets?  Are they manufactured media or are
they just burnt CDs?  Who sells these?



http://www.freebsdmall.com/cgi-bin/fm


Under which licence is FreeBSD released?  Where can a copy of this be located
on the web?


http://www.freebsd.org/copyright/freebsd-license.html


When will FreeBSD version 6.0 be released?


http://www.freebsd.org/where.html#helptest

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

Re: Console size

[Lowell Gilbert]

"Jared Feider" <[EMAIL PROTECTED]> writes:

> I am new to bsd.  When I boot my dell Latitude C610 the console much smaller
> than the full screen would allow.  When I start X it does go full screen.  I
> know in Linux I could run lilo to change the console settings.  What would
> be the parallel in FreeBSD 5.4?

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

Re: Which version of FreeBSD a binary was compiled for?

[Micah]

Andrew P. wrote:

On 10/27/05, Joshua Tinnin <[EMAIL PROTECTED]> wrote:


On Wed 26 Oct 05 09:18, "Andrew P." <[EMAIL PROTECTED]> wrote:


On 10/26/05, Robert Huff <[EMAIL PROTECTED]> wrote:


Andrew P. writes:


> file /usr/bin/man
>
> on my machine outputs:
>
> /usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version
> 1 (FreeBSD), for FreeBSD 5.4-CURRENT (rev 3), dynamically
> linked (uses shared libs), stripped

Oh, it's just that file hasn't leared anything about
FreeBSD 6 yet, so it doesn't display version info
when run against my binaries.


   Curious.

huff@> file /usr/bin/man
/usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1
(FreeBSD), for FreeBSD 7.0 (73), dynamically linked (uses
shared libs), stripped huff@>


I tried both versions of file (base system and ports)
on 6.0 RC1, none showed any info about that
/usr/bin/man (or any other system binary I tried).

On my firewall (5.4) it works.


That's odd. Am on 6.0-RC1:

# uname -a
FreeBSD smogmonster.local 6.0-RC1 FreeBSD 6.0-RC1 #0: Thu Oct 20
14:41:23 MDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL60  i386

% file /usr/bin/xargs
/usr/bin/xargs: ELF 32-bit LSB executable, Intel 80386, version 1
(FreeBSD), for FreeBSD 6.0 (600034), dynamically linked (uses shared
libs), stripped

% file /usr/bin/man
/usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1
(FreeBSD), for FreeBSD 6.0 (600034), dynamically linked (uses shared
libs), stripped

% file /bin/echo
/bin/echo: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),
for FreeBSD 6.0 (600034), dynamically linked (uses shared libs),
stripped


I know I built valgrind just a few days ago:

% file /usr/local/bin/valgrind
/usr/local/bin/valgrind: ELF 32-bit LSB executable, Intel 80386, version
1 (FreeBSD), for FreeBSD 6.0 (600034), statically linked, stripped

vim, too:

% file /usr/local/bin/vim
/usr/local/bin/vim: ELF 32-bit LSB executable, Intel 80386, version 1
(FreeBSD), for FreeBSD 6.0 (600034), dynamically linked (uses shared
libs), stripped


I'm not sure what it means when this information isn't accessible, but
I'd say it's symptomatic of another issue, and most likely it's not
good. If you built from source, did you follow the procedure described
in the handbook?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

Not sure, but are you installing kernel after building world, and then
installing world in single user? I've seen strange things happen if you
don't do this procedure the right way. Of course, I'm just guessing, as
I'm not at all sure what could be causing this problem or what your
exact circumstances are.

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




sat64% uname -a
FreeBSD sat64.net17 6.0-RC1 FreeBSD 6.0-RC1 #2: Fri Oct 14 22:57:08 MSD 2005
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SATCUR32  i386

sat64% file /usr/bin/xargs
/usr/bin/xargs: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dyn
amically linked (uses shared libs), stripped

sat64% file /usr/bin/man
/usr/bin/man: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynam
ically linked (uses shared libs), stripped

sat64% file /bin/echo
/bin/echo: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamica
lly linked (uses shared libs), stripped

sat64% file /usr/local/bin/waveplay
/usr/local/bin/waveplay: ELF 32-bit LSB executable, Intel 80386, version 1 (Free
BSD), dynamically linked (uses shared libs), stripped

sat64% file /usr/local/lib/oss/bin/ossplay
/usr/local/lib/oss/bin/ossplay: ELF 32-bit LSB executable, Intel 80386, version
1 (FreeBSD), dynamically linked (uses shared libs), stripped

sat64% /usr/local/bin/file /usr/local/lib/oss/bin/ossplay
/usr/local/lib/oss/bin/ossplay: ELF 32-bit LSB executable, Intel 80386, version
1 (FreeBSD), dynamically linked (uses shared libs), stripped


Maybe you're right. I never go to single-user when
upgrading. But then, I'm the only user and there are
not many processes. I'm not gonna worry anyway,
hope it's not a rootkit :-)


I have a 5.4 system, /do/ go into single user when upgrading, and file 
does /not/ report FreeBSD version.  I get the same output you do.  It 
would be nice to know why this works on some systems and not on others.


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

packet forwarding

[Yance Kowara]

Hi all,

What's the difference between 

gateway_enable="YES" in /etc/rc.conf

and

net.inet.ip.forwarding=1 in /etc/sysctl.conf

Regards,

Yance



__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: packet forwarding

[Igor Robul]

Yance Kowara wrote:


Hi all,

What's the difference between 


gateway_enable="YES" in /etc/rc.conf

and

net.inet.ip.forwarding=1 in /etc/sysctl.conf

Regards,
 

There are no differences, you can check this by greping gateway_enable  
in /etc/rc.d/*.


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

Re: packet forwarding

[Dan Nelson]

In the last episode (Oct 27), Yance Kowara said:
> What's the difference between 
> 
> gateway_enable="YES" in /etc/rc.conf
> 
> and
> 
> net.inet.ip.forwarding=1 in /etc/sysctl.conf

>From /etc/rc.d/routing:

case ${gateway_enable} in
[Yy][Ee][Ss])
echo -n ' IP gateway=YES'
sysctl net.inet.ip.forwarding=1 >/dev/null
;;
esac

So the answer is: nothing, except that adding the line to sysctl.conf
enables packet forwarding before interfaces are configured and other
network variables are set, so you may get spurious "host unreachable"
errors from systems trying to route through the box when it boots up.

-- 
Dan Nelson
[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: /dev/kqemu

[dick hoogendijk]

On Mon, 24 Oct 2005 21:22:00 -0500
Eric Schuele <[EMAIL PROTECTED]> wrote:

> dick hoogendijk wrote:

> > I have found out that only the FIRST user that starts QEMU on ht
> > computer gets support for kqemu accellaration. Even if he closes hiw
> > qemu session and logs off, another NEW user can start QEMU but gets
> > NO accel support. The above error is put on the screen.
> > 
> 
> Hmmm... after reading this post... I wondered if that was the problem
> I was experiencing.  But I retested on RELENG_6, and I am not seeing
> this behavior.
> 
> Is that your 4.x or your 5.x machine behaving that way?

Both.
FreeBSD-4.11-stable and FreeBSD-5.4(latest patch)

-- 
dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4
+ Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Qwest DLS & MSN Premium & Linksys Router & FreeBSD.. Oh my

[Kris Anderson]

--- "Gary W. Swearingen" <[EMAIL PROTECTED]> wrote:

> Kris Anderson <[EMAIL PROTECTED]> writes:
> 
> > I'm getting off cable (Comcast and 6 megabits) and
> 
> Good move.
> 
> > Their fine print -
> 
> Don't forget the finer print.  "Invisible print"
> might be a better
> term; good luck even finding it before committing
> yourself.  More
> below.
> 
> > home phone pac kage ($24.99 otherwise), free
> 
> Check out which "phone pac" that is.  I doubt very
> much if regular
> phone service is considered to be a home phone pac;
> I mangaged to find
> (after considerable searching) their page for
> ordering non-pac phone
> service to get a 12.50 basic service (before more
> than that in various
> fees and taxes, one which seems to be part of
> _their_ taxes -- grrr).
> 
> > restrictions may apply. MSN ISP requires agreement
> to
> > MSN Acceptable Use Policy.
> 
> Yeah, after considerable searching I found a "MSN
> Subscription
> Agreement" link at http://support.msn.com/ which
> took me to a member
> sign-in form.  Do you really want to do business
> with a company that
> does business like that?
> 
> > So am I right in still thinking that with MSN as
> the
> > ISP my setup it isn't going to be FreeBSD friendly
> and
> > that my spiffy little Comcast setup isn't going to
> > work with MSN as the ISP?
> 
> I can't help you; and I wouldn't help MSN if I
> could.  I know I
> first bought a (used) modem that was "guaranteed" to
> work with
> Qwest and a non-MSFT ISP, but I later learned that
> it would only
> work with Qwest+MSN and had to pay a "restocking"
> fee to get most
> of my money back.  Grrr.
> 
> 
> I found what seems (in about 5 mo) to be a good ISP
> at opusnet.com .
> Relatively good contract terms and in actual
> practice, so far.  And
> about as cheap as they come.
> 
> 
> Note that _almost_ all ISPs have indemnity clauses
> whereby you agree
> to pay their legal and other costs if some third
> party makes claims
> against the ISP which involve you in any way,
> whether or not you've
> done anything wrong in most such clauses.  Another
> facter is how far
> away the courthouse and your lawyer would be.
> 
> Last time I looked, Quest had no indemnity clause
> for their pure DSL
> service, but they had one in their ISP contract and,
> of course, MSN
> does too.  I say "of course", but I should note that
> MSN.net is one of
> increasingly-few web sites that has no indemnity
> clause in the
> site-use contract.  Even such "open source" sites as
> Slashdot have
> them these days.  I assume the risk of using such
> sites in read-only
> mode, but seldom, if ever, post anything to them. 
> BTW, my insurance
> guy knows of no personal insurance against such
> indemnity risks.
> 
> 
> I bought a DSL modem at Fry's for about 10 $ more
> than Qwest's, mostly
> because Qwest has given me many reasons to dislike
> and distrust them
> and partly because my modem has a 2-yr guarantee. It
> is a Zoom ADSL X5
> and seems to work fine and was easy to configure
> once I got past some
> problem that I had with Mozilla not accessing the
> modem's
> configuration web forms correctly.  (I've already
> forgotten the
> cause.)  Beware that the Zoom modem package says in
> big print that it
> comes with DSL filters and in fine print it says how
> many it comes
> with, which I didn't notice was _zero_. Grrr.)
> 
> With the Zoom modem, at least, you may configure it
> to run DHCP and
> give the modem a fixed (eg, 10.something) IP address
> or run DHCP on
> whatever you connect to the modem.  The Zoom X5 is
> also a 4-port
> router, but this one was not wireless like the Qwest
> modem.
> 
> 
> Finally, beware that a few weeks ago DSL providers
> like Qwest got
> permission (from the US gov) to refuse to do
> business (after 2005,
> IIRC) with good ISPs like opusnet.com, so don't be
> suprised if your
> choice in 2006 is between Qwest+MSN and
> Comcast+Comcast.  Grr.
> 
>-- Grry
> ___
> freebsd-questions@freebsd.org mailing list
>
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
> 
Wowzers, I think I'll get a couple of tin cans and a
string.

Thanks Gary, and everybody else who replied. Most
appreciated.

~Mr. Anderson




__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

packages for older 4.x systems

[Alex Kapranoff]

Hello!

I'm trying to install cvsup on an older system: 4.11-RELEASE-p3.

`pkg_add -r cvsup-without-gui' fails so I downloaded this file manually:
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/net/cvsup-without-gui-16.1h_2.tgz

pkg_add fails too:
pkg_add: read_plist: bad command '@conflicts cvsup-[0-9]*'

I tried to install ports/sysutils/pkg_install (that was 
pkg_install-20050720.tar.gz),
but it didn't help.

So the question is, how do I pkg_add official binary packages on a
4.11-p3 box?

-- 
Alex Kapranoff,
$n=["1another7Perl213Just3hacker49"=~/\d|\D*/g];
$$n[0]={grep/\d/,@$n};print"@$n{1..4}\n"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Which version of FreeBSD a binary was compiled for?

[Will Maier]

On Thu, Oct 27, 2005 at 06:51:21AM -0700, Micah wrote:
> I have a 5.4 system, /do/ go into single user when upgrading, and
> file does /not/ report FreeBSD version.  I get the same output you
> do.  It would be nice to know why this works on some systems and
> not on others.

Consider diff'ing the /usr/share/misc/magic file from a system that
works and a system that doesn't work. I'd expect the difference to
be evident there.

It works find on all my machines, though.

-- 

o--{ Will Maier }--o
| jabber:[EMAIL PROTECTED] | email:[EMAIL PROTECTED] |
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*

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

Hardware Donation?

[Darren Sessions]

I am wondering if the FreeBSD project is in need of any server hardware.
If so, I would like to make a donation.

Thanks,

 - Darren

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

Re: Hardware Donation?

[Mark Kane]

Darren Sessions wrote:

I am wondering if the FreeBSD project is in need of any server hardware.
If so, I would like to make a donation.

Thanks,

 - Darren


Hi Darren. Here is a list of some hardware that the FreeBSD team is 
looking for:


http://www.freebsd.org/donations/wantlist.html

I think it's really nice to donate to such a great project, so I'm sure 
they will really appreciate your help :)


-Mark

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

Re: Hardware Donation?

[Andrew P.]

On 10/27/05, Darren Sessions <[EMAIL PROTECTED]> wrote:
> I am wondering if the FreeBSD project is in need of any server hardware.
> If so, I would like to make a donation.
>
> Thanks,
>
>  - Darren
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

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

RE: Qwest DLS & MSN Premium & Linksys Router & FreeBSD.. Oh my

[Ted Mittelstaedt]

>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Kris Anderson
>Sent: Monday, October 24, 2005 8:48 PM
>To: [EMAIL PROTECTED]
>Subject: Qwest DLS & MSN Premium & Linksys Router & FreeBSD.. Oh my
>
>
>Hey folks,
>
>I'm getting off cable (Comcast and 6 megabits) and
>either looking at Qwest DSL w/MSN premium or a service
>called Clear Wire (Wireless internet).
>

>
>Just to confirm, my guess is that this would not be
>the service to go with since I would love to have my
>spiffy Linksys Router (WRT-54G) hook to the DSL. And
>to the WR54G the usual network systems of FreeBSD, and
>misc Windows computers.
>

Not a problem many people on MSN do that.  No static
IP address, though.

But consider a commercial ISP that provides service over
the Qwest DSL network.  You will get better service and
tech support won't be scratching their head if you mention
the word FreeSBD when you call in.

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

Scan for viruses!

[Carstea Catalin]

Hi there!
I want to scan all traffic going through wan - interface for viruses?
Any recommendation?
P.S: my freebsd box is router of my network!
--
Any help would be greatly appreciated.
regards,
Carstea Catalin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Scan for viruses!

[Rob Pitt]

amavis

On 27 Oct 2005, at 18:40, Carstea Catalin wrote:


Hi there!
I want to scan all traffic going through wan - interface for viruses?
Any recommendation?
P.S: my freebsd box is router of my network!
--
Any help would be greatly appreciated.
regards,
Carstea Catalin
___
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: Scan for viruses!

[Kilaru Sambaiah]

Carstea Catalin wrote:


Hi there!
I want to scan all traffic going through wan - interface for viruses?
Any recommendation?
P.S: my freebsd box is router of my network!
--
Any help would be greatly appreciated.
regards,
Carstea Catalin
___
 


All trafic? All ports? Http, ftp, smtp, pop3 etc
If you have $$$, viruswall is the solution.
sam


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

Re: Which version of FreeBSD a binary was compiled for?

[Micah]

Will Maier wrote:

On Thu, Oct 27, 2005 at 06:51:21AM -0700, Micah wrote:


I have a 5.4 system, /do/ go into single user when upgrading, and
file does /not/ report FreeBSD version.  I get the same output you
do.  It would be nice to know why this works on some systems and
not on others.



Consider diff'ing the /usr/share/misc/magic file from a system that
works and a system that doesn't work. I'd expect the difference to
be evident there.

It works find on all my machines, though.



I have two 5.4 systems, one's a 5.4-Release installed from Disk, the 
other's a 5.4-release-p7 upgraded from 5.3 via the procedures in the 
handbook.  File on the former reports FreeBSD version, file on the 
latter does not.  There appears to be only minor differences in magic 
files between the two machines.  Copying the magic file from the working 
machine to the non-working machine and compiling it via file -c did not 
change anything.  Copying the executable from the working machine to the 
non-working machine did nothing either.


Note: alexis->5.4, trisha->5.4p7

alexis% file `which ethereal`
/usr/X11R6/bin/ethereal: ELF 32-bit LSB executable, Intel 80386, version 
1 (FreeBSD), for FreeBSD 5.4, dynamically linked (uses shared libs), 
stripped


trisha% file `which ethereal`
/usr/X11R6/bin/ethereal: ELF 32-bit LSB executable, Intel 80386, version 
1 (FreeBSD), dynamically linked (uses shared libs), stripped


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

Re: math/grace port: "libXcursor.so.1.0" not found ?? [FBSD/Xorg error?]

[Kris Kennaway]

On Thu, Oct 27, 2005 at 04:00:55AM -0700, Rob wrote:

> Here is the two points response from the grace
> mailinglist:
> 
> 
> 1. Because XOpenDisplay() causes dlerror() to be
>set:
>One of the FreeBSD X libraries is broken,
>calling an inexisting libXcursor.so.1.0.
> 
> 2. The FreeBSD dynamic loader is broken, ignoring
>unresolved references in DLLs both at
>initialization and run time.
> 
> 
> So is the libX11.so.6 on FreeBSD (or another) to be
> blamed?

Talk to the xorg maintainers ([EMAIL PROTECTED]).  I suspect there are
two problems: the libXcursor.so.1.0.2 reference in the x library,
which should not be there, and a bug in xmgrace for not correctly
handling dlerror(), as Igor has been explaining.  xmgrace should be
robust enough to handle the case of some other application having
failed to dlopen() something, instead of assuming it has perfect
knowledge of the program state.

Kris


pgpGUjiJQWuO3.pgp
Description: PGP signature

Re: Unable to upgrade kdenetwork using portupgrade

[Kris Kennaway]

On Thu, Oct 27, 2005 at 09:06:36AM -0400, Teo De Las Heras wrote:
> I'm running FreeBSD 5.4 on my dektop with X.org  and KDE 3.4.
> I'm synchronizing my ports tree using cvsup.
>  When I run the following command
>  portupgrade -rR kdenetwork
>  It fails because it is unable to upgrade the kdelibs. The error messages
> says to run -F to force.

It doesn't say that, it says a complete error message.  What is it?

>  What is the consequence?
>  Would it be simpler to run portupgrade -rR kde?

Read /usr/ports/UPDATING - there are special steps you need to go
through when updating kde.

Kris


pgpAKSc5KoWC1.pgp
Description: PGP signature

Re: packages for older 4.x systems

[Kris Kennaway]

On Thu, Oct 27, 2005 at 07:36:26PM +0400, Alex Kapranoff wrote:
> Hello!
> 
> I'm trying to install cvsup on an older system: 4.11-RELEASE-p3.
> 
> `pkg_add -r cvsup-without-gui' fails so I downloaded this file manually:
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/net/cvsup-without-gui-16.1h_2.tgz
> 
> pkg_add fails too:
> pkg_add: read_plist: bad command '@conflicts cvsup-[0-9]*'
> 
> I tried to install ports/sysutils/pkg_install (that was 
> pkg_install-20050720.tar.gz),
> but it didn't help.
> 
> So the question is, how do I pkg_add official binary packages on a
> 4.11-p3 box?

Stick to the 4.11-release packages, use ports, or update to
4.11-stable.

Kris


pgp3sVu4e4nlz.pgp
Description: PGP signature

Re: Window scaling

[Daniel Gonzalez]

>
> "Do you think that it is possible to modify parameters on the BSD box in
> order to reach the same transfer rates than the Debian box with only one
> connection ?"


I would think there may be options you can pass to the ethernet driver via
ifconfig or maybe adjusting net related sysctls. You could try this

REDE2SRV# sysctl -h -a | grep 'net.*'

 That will give you a dump of network related tunable kernel parameters.
Other than that, I would need to see a dmesg (or the relevant boot messages
for you nic)

Hope that helps

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

Re: Which version of FreeBSD a binary was compiled for?

[Micah]

Will Maier wrote:

On Thu, Oct 27, 2005 at 06:51:21AM -0700, Micah wrote:


I have a 5.4 system, /do/ go into single user when upgrading, and
file does /not/ report FreeBSD version.  I get the same output you
do.  It would be nice to know why this works on some systems and
not on others.



Consider diff'ing the /usr/share/misc/magic file from a system that
works and a system that doesn't work. I'd expect the difference to
be evident there.

It works find on all my machines, though.



Didn't think to check this until /after/ I started to make lunch. :)  I 
copied ethereal from the working machine to the non-working machine. 
Using file on the copied ethereal gives me:


trisha% file ethereal
ethereal: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), 
for FreeBSD 5.4, dynamically linked (uses shared libs), stripped


Conversly coping ethereal from the broken machine to the working machine 
I get:


alexis% file ethereal
ethereal: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), 
dynamically linked (uses shared libs), stripped


In other words, it's not file that broken, but /every/ executable on the 
broken machine is broken.  Now why would that be?  A compiler flag or 
something?


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

Re: Which version of FreeBSD a binary was compiled for?

[Will Maier]

On Thu, Oct 27, 2005 at 11:36:18AM -0700, Micah wrote:
> In other words, it's not file that broken, but /every/ executable
> on the broken machine is broken.  Now why would that be?  A
> compiler flag or something?

Must be -- some flag produces unique bits in the executables. I'm a
little surprised there isn't (AFAICT) anything descriptive in
file(1)'s manpage or /u/s/mi/magic that would explain the
discrepancy. Didn't see anything in quick looks through gcc(1) or
make(1), either.

Weird.

-- 

o--{ Will Maier }--o
| jabber:[EMAIL PROTECTED] | email:[EMAIL PROTECTED] |
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*

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

Re: /dev/kqemu

[Eric Schuele]

dick hoogendijk wrote:

On Mon, 24 Oct 2005 21:22:00 -0500
Eric Schuele <[EMAIL PROTECTED]> wrote:



dick hoogendijk wrote:




I have found out that only the FIRST user that starts QEMU on ht
computer gets support for kqemu accellaration. Even if he closes hiw
qemu session and logs off, another NEW user can start QEMU but gets
NO accel support. The above error is put on the screen.



Hmmm... after reading this post... I wondered if that was the problem
I was experiencing.  But I retested on RELENG_6, and I am not seeing
this behavior.

Is that your 4.x or your 5.x machine behaving that way?



Both.
FreeBSD-4.11-stable and FreeBSD-5.4(latest patch)



Wish I had a solution for you.  FWIW... if you can find no other 
solution try the port maintainer.  I did when I had difficulties... and 
he was very responsive and eager to assist.


HTH.

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

Re: Which version of FreeBSD a binary was compiled for?

[David Kirchner]

On 10/27/05, Will Maier <[EMAIL PROTECTED]> wrote:
> Must be -- some flag produces unique bits in the executables. I'm a
> little surprised there isn't (AFAICT) anything descriptive in
> file(1)'s manpage or /u/s/mi/magic that would explain the
> discrepancy. Didn't see anything in quick looks through gcc(1) or
> make(1), either.
>
> Weird.

It doesn't look like it's done in the magic file. Rather, it's
something built in to file itself. Check out around line 400 of
'readelf.c'.

This doesn't explain how it gets in to the binaries built, though.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

increasing mount size

[eoghan]

Hello
My /var mount has no more space left. I was wondering if there is  
some way to increase the size of it without loosing anything?

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

Re: increasing mount size

[Roland Smith]

On Thu, Oct 27, 2005 at 08:28:12PM +0100, eoghan wrote:
> Hello
> My /var mount has no more space left. I was wondering if there is  
> some way to increase the size of it without loosing anything?

That depends.

If you have enough free space left on your harddrive, you could make a
new slice, copy /var there, unmount the old /var,
and remount the new /var.

Another option is to copy everything in /var to another directory on
another slice that has enough space, unmount /var and make it a symlink
to the new location.

All these tricks are best done in single user mode.

Roland
-- 
R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text.
public key: http://www.xs4all.nl/~rsmith/pubkey.txt


pgpExZcokVBAX.pgp
Description: PGP signature

Apache::DBI Problems

[Cody Holland]

I'm having some major issues with perl site I'm trying to get working.
I'm running FreeBSD 5.4 stable using Apache 2.0.55 and perl 5.8.7.  The
error I'm getting is:
Can't locate object method "connect_on_init" via package "Apache::DBI"
(perhaps you forgot to load "Apache::DBI"?)

I do have 
LoadModule perl_module libexec/apache2/mod_perl.so
PerlModule Apache::DBI
in my httpd.conf file.  I'm pretty new to perl and have no idea what
I've done wrong.  Any help would greatly be appreciated.  If you need
more info from me, don't hesitate to ask.

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

Hot-Swap HDD hardware recommendations?

[Eric F Crist]

Hello list,

I need a cost-effective solution for hot-swap hard drives.  I'm  
currently using a removable drive cage available at any CompUSA, but  
it's standard IDE/ATA, which is, AFAIK, not hot-swappable.  What kind  
of RAID hardware/software would I need so that I can hot swap hard  
drives?


TIA

___
Eric F Crist  "I am so smart, S.M.R.T!"
Secure Computing Networks  -Homer J Simpson

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

Re: increasing mount size

[Andrew P.]

On 10/27/05, eoghan <[EMAIL PROTECTED]> wrote:
> Hello
> My /var mount has no more space left. I was wondering if there is
> some way to increase the size of it without loosing anything?
> Thanks
> Eoghan
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

FreeBSD default layout is very smart.

What takes up so much in your /var?

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

Re: increasing mount size

[eoghan]

On 27 Oct 2005, at 22:32, Andrew P. wrote:


On 10/27/05, eoghan <[EMAIL PROTECTED]> wrote:


Hello
My /var mount has no more space left. I was wondering if there is
some way to increase the size of it without loosing anything?
Thanks
Eoghan
___
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 default layout is very smart.

What takes up so much in your /var?

# du -s /var/*


That says:
du: No match.
im not sure :) but i was trying to add openoffice... i know its big.  
the size of my var is only 248MB, which

is the same size as /tmp and ive only 2% left on that.
its a 20GB hard drive - i suppose these days thats pretty small.

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

linux: command not found

[Mark Bucciarelli]

I'm trying to load the linux kernel module to install java.

When I type linux, I get a command not found error.

Do I need to install a port or is this an issue with my kernel 
configuration?

m

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

Re: increasing mount size

[eoghan]

On 27 Oct 2005, at 23:03, eoghan wrote:



FreeBSD default layout is very smart.

What takes up so much in your /var?

# du -s /var/*



That says:
du: No match.
im not sure :) but i was trying to add openoffice... i know its  
big. the size of my var is only 248MB, which

is the same size as /tmp and ive only 2% left on that.
its a 20GB hard drive - i suppose these days thats pretty small.


oops! typo... sorry... output:
nathaniel# du -s /var/*
2   /var/account
6   /var/at
8   /var/backups
4   /var/crash
4   /var/cron
71010   /var/db
2   /var/empty
2   /var/games
2   /var/gdm
2   /var/heimdal
6   /var/lib
720 /var/log
2   /var/mail
4   /var/msgs
38  /var/named
2   /var/preserve
42  /var/run
2   /var/rwho
24  /var/spool
4844/var/tmp
20  /var/yp
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: increasing mount size

[David Kirchner]

On 10/27/05, eoghan <[EMAIL PROTECTED]> wrote:
> oops! typo... sorry... output:
> nathaniel# du -s /var/*
> 2   /var/account
> 6   /var/at
> 8   /var/backups
> 4   /var/crash
> 4   /var/cron
> 71010   /var/db

This is probably because the port uses /var/db/mysql as the database
directory (not sure why since /var is pretty tiny). An easy "fix" is:

mysqladmin shutdown
mkdir /usr/local
mv /var/db/mysql /usr/local/
ln -s /usr/local/mysql /var/db/mysql

then start mysqld however it is you do that (mysql-server.sh start maybe?)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: linux: command not found

[David Kirchner]

On 10/27/05, Mark Bucciarelli <[EMAIL PROTECTED]> wrote:
> I'm trying to load the linux kernel module to install java.
>
> When I type linux, I get a command not found error.
>
> Do I need to install a port or is this an issue with my kernel
> configuration?

The "linux" script is no longer in FreeBSD -- you can load linux.ko by running:

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

Re: increasing mount size

[eoghan]

On 27 Oct 2005, at 23:22, David Kirchner wrote:


On 10/27/05, eoghan <[EMAIL PROTECTED]> wrote:


oops! typo... sorry... output:
nathaniel# du -s /var/*
2   /var/account
6   /var/at
8   /var/backups
4   /var/crash
4   /var/cron
71010   /var/db



This is probably because the port uses /var/db/mysql as the database
directory (not sure why since /var is pretty tiny). An easy "fix" is:

mysqladmin shutdown
mkdir /usr/local
mv /var/db/mysql /usr/local/
ln -s /usr/local/mysql /var/db/mysql

then start mysqld however it is you do that (mysql-server.sh start  
maybe?)


Ah, thats much better now. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

libtool: link: `/hsphere/shared/lib/libiconv.la' is not a valid libtool archive

[Pang]

Hello Everyone,
 I have tried to compile PHP4.4.0 and got the following error:

grep: /hsphere/shared/lib/libiconv.la: No such file or directory
sed: /hsphere/shared/lib/libiconv.la: No such file or directory
libtool: link: `/hsphere/shared/lib/libiconv.la' is not a valid libtool 
archive


 I have tried to reinstall libtool and libiconv, but the problem is not 
fixed. Could you tell me which port install libiconv.la?


 My FreeBSD version is 5.4

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

Re: increasing mount size

[Jerry McAllister]

> 
> Hello
> My /var mount has no more space left. I was wondering if there is  
> some way to increase the size of it without loosing anything?

This is a frequent question on the list.   There might even be a FAQ on
it.   You might check.   I know I have written numerous responses to
essentially the same question.

The first thing to do is find out what is using up all the space.
In /var, it may well be log files that are outdated and can be
thrown away, or stuff stuck in /var/spool that never goes anywhere,
or something of that nature.

To start checking, go in to that directory and run du(1)
  cd /var
  du -sk *
Then if you see a directory that seems abnormally large, go in
to it and run du again until you get a clearer picture of what
is using the space and if it is something you need to keep or
can just nuke.

Presuming you need to keep enough of the stuff that it won't free
up enough space for you, you have two options.   One is to get 
a larger or additional disk.Another is to look for a existing
file system that isn't getting much use.

If you have enough extra space somewhere else such as in a /junk
file system you made way back, just for something to do with extra 
space, then you can move the biggest consumers of space there and make 
symlinks.Lets say /var/spool is gobbling scads of space and
you want to move it in to /junk
Go to /junk and create a directory for it - say var.spool
tar stuff up and move it
check it for peace of mind
make the symlink
clean up

  cd /junk
  mkdir var.spool
  cd /var/spool
  tar cvpf /junk/varspool.tar *
  cd /junk/var.spool
  tar xvpf ../varspool.tar

Look at stuff to make sure it is cool.

  cd /var
  mv spool spool.old
  ln -s /junk/var.spool spool

Check things out some more.   At this stage, it should all be
working from the copy in /junk/var.spool
If you do a cd /var/spool and then a pwd you should see that
you are really in /junk/var.spool

Then clean up.
  cd /var
  rm -rf spool.old
  cd /junk
  rm varspool.tar

Voila - lots of space now in var and room for spool to grow as well.

Note that the way I describe is somewhat due to lack of confidence
in stuff.   It results in three copies of /var/spool for a short
time until you clean up.   You could pipe the one tar in to another
and it would work fine and leave you with just two copies until cleanup.

I also explain it this way, because it is more straightforward to
understand.

If you add a disk, fdisk, disklabel/bsdlabel and newfs it to
get a filesystem, then the process of moving some part of /var
there is exactly the same.  Only the names (of where you are putting
it) change a little.

If you add a disk and make a big file system on it just for /var
then use dump(8) and restore(8) to move the old /var to the
new file system and then just edit /etc/fstab so that the 
new file system gets mounted as /var instead of the old one.

Let's presume your current /var is /dev/da0s1e.
Let's also say you created a /dev/da1s1f (amongst possibly others) 
with lots of room and you want to put /var there.   

  cd /
  mkdir tmpvar  (Could probably use /mnt but I usually 
  mount /dev/da1s1f /tmpvar  already have that one tied up elsewhere)
  cd /tmpvar
  dump 0af - /var | restore rf -

Then edit /etc/fstab so that the previous line:

  /dev/da0s1e  /var ufs rw   2   2

Now looks like:

  /dev/da1s1f  /var ufs rw   2   2

Then you remount /var

  umount /var
  mount /var

I think you can just domount -u /var

Now it will be using the new one and you have some left over space
on the old disk (/dev/da0s1e) to decide what to do with.  You can
use it as scratch space.

  cd /
  mkdir scratch
  mount /dev/da0s1e /scratch

Make an /etc/fstab entry that looks like:  
  
  /dev/da0s1e  /scratch ufs rw   2   2

And it will mount on boot.

If your current /var is not its own separately mounted filesystem - but
really just a part of /root, which is most often the case, then you will 
not be able to use dump/restore to move stuff.   You will need to use tar.   
But the rest is the same in that you create the new filesystem on the new 
disk.  Then put stuff there like we did with tar above when moving just
the /var/spool directory except you move the whole /var instead of just
/var/spool.   

Then make the entry in /etc/fstab.   

But, before mounting it, rename the old /var and make a new mount
point - somewhat like we did above when moving just /var/spool.

  cd /
  mv /var /var.old
  mkdir var
  mount /dev/da1s1f /var

Now you can clean up the old space

  cd /
  rm -rf var.old

That will automatically return all that space to the /root filesystem.

jerry

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

Intel Mother card

[Albert Shih]

Hi All

I've a server under FreeBSD 5.4-stable.

On front of this server I've red led. This led is on now, I'm sure this
informe my there're a hardware problem. But I don't know what's wrong with
this server.

I search some software can check for my the hardware.

The mother card is a Intel mothercard. The server is a Sun (I think V60)
with Intel Xeon

Anyone can help me ?

Regards.


--
Albert SHIH
Universite de Paris 7 (Denis DIDEROT)
U.F.R. de Mathematiques.
7 i?me ?tage, plateau D, bureau 10
Heure local/Local time:
Fri Oct 28 02:17:03 CEST 2005
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: portupgrade stale dependencies

[John DeStefano]

On 10/27/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> On 10/27/05, John DeStefano <[EMAIL PROTECTED]> wrote:
> >
> > After clearing out the ports, updating ports (with portsnap) and
> > source, and rebuilding the system and kernel... it seemed the ultimate
> > problem was actually a dependency of the package to apache1.3. After I
> > ran 'pkgdb -F' and "fixed" this dependency to point to apache2.1, but
> > I still had trouble installing ports.
> >
> > 'portsdb -Uu' would not run, so I ran 'make fetchindex' and
> > 'portupdate -a'.  From what I've read, this _should_ create an index
> > and update all out-of-date ports and their dependencies, but it never
> > has worked for me.  I just tried this combination again, and it
> > (again) punts during portupdate.  This time, 38 ports were skipped and
> > 7 failed, the first failure being a strange compiler error in updating
> > from apache-2.0.48.
> >
> > I've been fighting with ports for long enough now to have become a bit
> > frustrated with them.  If you have any thoughts or suggestions on how
> > to troubleshoot them, please pass them on.
> >
> > Thanks,
> > ~John
> >
>
> Do not fix dependencies if you're not sure that they
> are really broken. Don't use apache21 unless 2.0
> is absolutely inappropriate. The proper way to change
> dependencies from apache1 to apache2 is to add
> "WITH_APACHE2=true" to /etc/make.conf (or to
> /usr/local/etc/pkgtools.conf, but that's an advanced
> topic).

I wasn't really looking to upgrade to apache21, just to update my
version (2.0.48) to any more current port, since other ports keep
barking about it being out-of-date.

I added the "WITH_APACHE2=true" parameter, but when I try to upgrade
my apache port, it seems to still be looking to the "wrong" version:
...Upgrading 'apache-2.0.48' to 'apache-2.1.4' (www/apache21)

This process attempts to build and then consistently fails with the
same error, which seems to my untrained eye like a C function error in
httpd:

ssl_engine_pphrase.c: In function `ssl_pphrase_Handle_CB':
ssl_engine_pphrase.c:684: error: `PEM_F_DEF_CALLBACK' undeclared
(first use in this function)
ssl_engine_pphrase.c:684: error: (Each undeclared identifier is
reported only once
ssl_engine_pphrase.c:684: error: for each function it appears in.)
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules/ssl.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules/ssl.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha/modules.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha.
*** Error code 1

Stop in /usr/ports/www/apache21/work/httpd-2.1.4-alpha.
*** Error code 1

Stop in /usr/ports/www/apache21.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade38050.3 make
** Fix the problem and try again.


Apparently, this is an OpenSSL-related bug, and there's a "patch"
availavble for it somewhere   Is there a way to fix this without
applying a patch?

> If you have portsdb utility, don't use make fetchindex,
> just add -F to portsdb: "portsdb -uUF" will work fine.

"portsdb -uU" wasn't working for me for a while, but I finally got it
going last night. Kris maintained that I should use "make fetchindex"
instead of "portsdb -uU" before running "portupgrade -a", at least
until my package installation dependencies were in better condition,
at which time I could resume using "portsdb -uU".  Problem is,
"portupgrade -a" still isn't working to update all installed packages
(most, but not all), regardless of whether it is preceded by "portsdb
-uU" or "portupgrade -a".

> You cann add -k to portupgrade, so that it doesn't
> skip ports (but it won't fix the failed ones).
>
> John, you'll have to spend a few hours reading
> ports documentation before you find them really
> great (which they really are).

I have no problem with reading as much documentation as I can find.
Aside from the handbook (Chapter 4, which is a nice overview) and man
pages (which are great for quick and complete reference), what else
would you recommend for gaining a more detailed understanding?  And I
do already agree that the port system is great, even with all the
trouble I'm having.

Thanks.

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

Re: portupgrade stale dependencies

[Eric F Crist]

On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:


On 10/27/05, Andrew P. <[EMAIL PROTECTED]> wrote:


On 10/27/05, John DeStefano <[EMAIL PROTECTED]> wrote:



After clearing out the ports, updating ports (with portsnap) and
source, and rebuilding the system and kernel... it seemed the  
ultimate
problem was actually a dependency of the package to apache1.3.  
After I
ran 'pkgdb -F' and "fixed" this dependency to point to apache2.1,  
but

I still had trouble installing ports.



At this point, what usually works for me is to:

#cd /usr && rm -rf ./ports

#mkdir ./ports && cvsup /root/ports-supfile

The above will delete your ENTIRE ports tree, provided it's kept in / 
usr/ports and as long as you use cvsup (and your ports supfile is / 
root/ports-supfile as mine is).  When a whole bunch of ports stop  
working, I find this is the easiest thing to do.


The other thing I do is run a cron job every week that updates, via  
cvsup, the ports tree.  About once a year I perform the above, mostly  
to clean out the crap.  Re-downloading your entire ports tree will be  
quicker if you don't use the ports-all tag and actually define which  
port segments you are interested in.  For example, there's no real  
reason to download all the x11/kde/gnome crap if you're doing this on  
a headless server that isn't going to serve X.


HTH
___
Eric F Crist  "I am so smart, S.M.R.T!"
Secure Computing Networks  -Homer J Simpson

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

Re: portupgrade stale dependencies

[Michael C. Shultz]

On Thursday 27 October 2005 18:49, Eric F Crist wrote:
> On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
> > On 10/27/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> >> On 10/27/05, John DeStefano <[EMAIL PROTECTED]> wrote:
> >>> After clearing out the ports, updating ports (with portsnap) and
> >>> source, and rebuilding the system and kernel... it seemed the
> >>> ultimate
> >>> problem was actually a dependency of the package to apache1.3.
> >>> After I
> >>> ran 'pkgdb -F' and "fixed" this dependency to point to apache2.1,
> >>> but
> >>> I still had trouble installing ports.
>
> At this point, what usually works for me is to:
>
> #cd /usr && rm -rf ./ports
>
> #mkdir ./ports && cvsup /root/ports-supfile
>
> The above will delete your ENTIRE ports tree, provided it's kept in /
> usr/ports and as long as you use cvsup (and your ports supfile is /
> root/ports-supfile as mine is).  When a whole bunch of ports stop
> working, I find this is the easiest thing to do.
>
> The other thing I do is run a cron job every week that updates, via
> cvsup, the ports tree.  About once a year I perform the above, mostly
> to clean out the crap.  Re-downloading your entire ports tree will be
> quicker if you don't use the ports-all tag and actually define which
> port segments you are interested in.  For example, there's no real
> reason to download all the x11/kde/gnome crap if you're doing this on
> a headless server that isn't going to serve X.
>
> HTH

Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
I may be a bit biased but I reaaly think John D. should try running 
portmanager -u (ports/sysutils/portmanager).  Stale dependencies is a non 
issue for portmanager.

-Mike

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

Re: Which version of FreeBSD a binary was compiled for?

[Micah]

David Kirchner wrote:

On 10/27/05, Will Maier <[EMAIL PROTECTED]> wrote:


Must be -- some flag produces unique bits in the executables. I'm a
little surprised there isn't (AFAICT) anything descriptive in
file(1)'s manpage or /u/s/mi/magic that would explain the
discrepancy. Didn't see anything in quick looks through gcc(1) or
make(1), either.

Weird.



It doesn't look like it's done in the magic file. Rather, it's
something built in to file itself. Check out around line 400 of
'readelf.c'.

This doesn't explain how it gets in to the binaries built, though.


Here's some more to think about.  I have a simple cpp program I used to 
test something a while back.  Running file on that executable returns:


trisha% file floatpoint
floatpoint: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), 
for FreeBSD 5.3.0, dynamically linked (uses shared libs), not stripped


I just now recompiled with "c++ floatpoint.cpp" and now:
trisha% file a.out
a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), 
dynamically linked (uses shared libs), not stripped


And compiled with same commandline on the "working" machine:
alexis% file a.out
a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for 
FreeBSD 5.4, dynamically linked (uses shared libs), not stripped


I looked at my "env", but I do not see /any/ compiler related variables 
set.  Is there something up with the compiler itself?  My processor? 
(Athlon64 in i386 mode)


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

help needed to fix Filesystem inconsistensy error

[rashmi ns]

Hello List,
As i were testing our kernel modules systems used to crash and reboot
ofently it you used to prompt that filesystem was inconsistent .then we ran
fsck_ffs /dev/ad0s1f and the filesystem was marked clean .When we did a
similar thing on the other drive which was also inconsistent we could not
fix the problem .
i ran fsck_ffs -b http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

True Type fonts

[Olivier Nicole]

Hi,

Is there any free source for True Type fonts (the common ones like
Times and etc) in order to use them with PDFLib.

TIA

Olivier


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

Re: Apache::DBI Problems

[Vladimir Tsvetkov]

> I'm having some major issues with perl site I'm trying to get working.
> I'm running FreeBSD 5.4 stable using Apache 2.0.55 and perl 5.8.7.  The
> error I'm getting is:
> Can't locate object method "connect_on_init" via package "Apache::DBI"
> (perhaps you forgot to load "Apache::DBI"?)
>
> I do have
> LoadModule perl_module libexec/apache2/mod_perl.so
> PerlModule Apache::DBI
> in my httpd.conf file.  I'm pretty new to perl and have no idea what
> I've done wrong.  Any help would greatly be appreciated.  If you need
> more info from me, don't hesitate to ask.

Maybe you should inspect the Perl script you're trying to run, and you
should look for the following Perl statement:

use Apache::DBI;

I think it's also good to read the documentation for the Apache::DBI
module in CPAN:
http://search.cpan.org/~pgollucci/Apache-DBI-0.9901/DBI.pm
You could also try to add

PerlModule Apache::DBI  # this comes before all other modules using DBI

to start.pl. You should pay attention to the comment!!!
THIS MODULE SHOULD BE LOADED BEFORE ALL OTHER MODULES USING DBI.

What can you do next if you had configured everything correctly and
the Perl scripts are OK?
Maybe you just dont't have the Apache::DBI module installed on your
machine, and you should download it and install it then:

% perl -MCPAN -e "shell"

install Apache::DBI

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

Re: math/grace port: "libXcursor.so.1.0" not found ?? [SOLVED]

[Rob]

--- Igor Robul <[EMAIL PROTECTED]> wrote:

> Rob wrote:
> 
> >---
> >   XtAppContext app_con;
> >   Display *disp = NULL;
> >   char *display_name = NULL;
> >
> >   XtSetLanguageProc(NULL, NULL, NULL); 
> >   XtToolkitInitialize();
> >   app_con = XtCreateApplicationContext();
> >
> >   disp = XOpenDisplay(display_name);
> >---
> >
> >(I have simplified this code snippet a bit, for
> >this example; also, grace uses Motif for its GUI).
> >
> >Before the XOpenDisplay() call, dlerror() does
> >not have the error-indicator set, but after
> >that call, it has.
> >  
> >
> I  wrote simple program to test XOpenDisplay +
> dlopen:
> 
> #include 
> #include 
> #include 
> 
> main(int argc, char **argv)
> {
> Display *d;
> void *handle;
> void *f;
> char *err;
> 
> if ((err=dlerror()) != NULL) {
> fprintf(stderr,"dlerror: %s\n",
> err);
> exit(1);
> }
> 
> d = XOpenDisplay(NULL);
> if (d == NULL) {
> fprintf(stderr, "Error in
> XOpenDisplay\n");
> exit(1);
> }
> 
> if ((err=dlerror()) != NULL) {
> fprintf(stderr, "dlerror: %s\n",
err);
> exit(1);
> }
> 
> XCloseDisplay(d);
> 
> handle = dlopen(argv[1], RTLD_NOW);
> if (handle == NULL) {
> fprintf(stderr, "dlopen: %s\n",
dlerror());
> exit(1);
> }
> 
> f = dlsym(handle, argv[2]);
> if (f == NULL) {
> fprintf(stderr, "dlsym: %s\n",
dlerror());
> exit(1);
> }
> 
> dlclose(handle);
> }
> 
> Compile it with
> gcc -o t t.c -I /usr/X11R6/include -L /usr/X11R6/lib
> -lX11
> 
> Then test with:
> ./t /usr/lib/libm.so pow
> 
> Then
> ./t /usr/lib/libm.so pow33
> dlsym: Undefined symbol "pow33"
> 
> So as you can see on my system all looks good. Try
> it on your system.
>

First:
NULL return from dlsym() does not always imply an
error. dlsym() can return NULL because it has an
empty list, but this does not set the error
indicator of dlerror(), because it is not an error.
However, if an error occurs, dlsym() has NULL as
a return (that's probably most sensible return).


Second:
I get different output than you, from this part
of the program:
 
 d = XOpenDisplay(NULL);
 if (d == NULL) {
  fprintf(stderr, "Error in XOpenDisplay\n");
  exit(1);
 }

 if ((err=(char *)dlerror()) != NULL) {
  fprintf(stderr, "dlerror: %s\n", err);
  exit(1);
 }

I get here:
dlerror: Shared object "nss_dns.so.1" not found,
 required by "t"

So apparently dlerror() is set by XOpenDisplay().

Hmmmyesterday I updated my world and kernel
to most recent 5-Stable, and after that I
recompiled all my ports. Still get this problem!

This is my /etc/make.conf:
---
CFLAGS= -O -pipe
NOPROFILE=true
NO_PF=true

CUPS_OVERWRITE_BASE=yes
NO_LPR=yes

WITHOUT_NLS=yes
WITHOUT_XFT=yes
DOC_LANG=en_US.ISO8859-1
WITH_ASPELL=yes
WITH_GTK2=yes
WITH_GIMP=yes
A4=yes

WITH_X11=yes

# added by use.perl 2005-10-26 14:20:09
PERL_VER=5.8.7
PERL_VERSION=5.8.7
---

Does that cause any problems?

Rob.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"