im getting ready to do a cvsup / build world from 4.9 to 5.3 , and im planning
on doing a custom kernnel build and i was whanting to find out if these
settings are still vallid in 5.3 and if not what the replacement is if any ,
and ive serched the mailing list and googled it and cant find exactly
On Mon, 06 Dec 2004 15:48:02 -0800, Paul Saab [EMAIL PROTECTED] wrote:
Arjan Van Leeuwen wrote:
I had a panic that looked a lot like this (panic in swi, came up when
I had some network traffic), and it's also been reported by other
people than me. Turning of SACK seems to work for most
This panic is reproducible:
# kldload smbfs
# mount some remote smbfs filesys
# mount the above remote smbfs filesys again
# mount the above remote smbfs filesys again
# umount the above remote smbfs filesys
# umount the above remote smbfs filesys again
# umount the above remote smbfs filesys
The patch at
http://people.freebsd.org/~glebius/totest/netgraph_callout
has been updated. Now it covers the following nodes:
ng_bridge.c
ng_l2tp.c
ng_lmi.c
ng_pppoe.c
ng_pptpgre.c
One more time I ask for testing. The patch can be applied both
On Mon, 6 Dec 2004 19:07:05 -0800 (PST), Doug White
[EMAIL PROTECTED] wrote:
On Mon, 6 Dec 2004, Arjan Van Leeuwen wrote:
(...)
The rate on 'clk' should be 1000, so it looks like your system doesn't
like HZ=1000. Try sticking this in loader.conf and rebooting:
kern.hz=100
If that works
Hi,
I'm the lucky owner of the ASUS SK8N (amd64) motherboard with
the onboard NVIDIA MCP Ethernet.
With this patch,
http://people.freebsd.org/~ru/patches/port_net_nvnet.patch
I'm happily running it for three days without any glitches
noticed so far:
: nv0: NVIDIA nForce MCP3 Networking
whitevamp wrote:
im getting ready to do a cvsup / build world from 4.9 to 5.3 , and im planning
on doing a custom kernnel build and i was whanting to find out if these
settings are still vallid in 5.3 and if not what the replacement is if any ,
and ive serched the mailing list and googled it and
Is there a best practice for automated updating large number of
interdependant ports? I keep my ports tree up-to-date, and sometimes I
wish to install applications that depend on a newer version of an
existing one, and fail.
My current example is gnome. Recently, whatever I want to install
Hi Ivan,
Tuesday, December 7, 2004, 4:47:23 PM, you Cannot open file C\TXT
COOKIES\reply-en.txt:
Is there a best practice for automated updating large number of
interdependant ports? I keep my ports tree up-to-date, and sometimes I
wish to install applications that depend on a newer version
Quoth Ivan Voras on Tue, Dec 07, 2004 at 16:47:23 +0100
Is there a best practice for automated updating large number of
interdependant ports? I keep my ports tree up-to-date, and sometimes I
wish to install applications that depend on a newer version of an
existing one, and fail.
## Ivan Voras ([EMAIL PROTECTED]):
Is there a best practice for automated updating large number of
interdependant ports? I keep my ports tree up-to-date, and sometimes I
wish to install applications that depend on a newer version of an
existing one, and fail.
portupgrade works in most
Hello,
Is there a best practice for automated updating large number of
interdependant ports? [..]
What about ports that have dialog boxes which require user intervention?
you can use /usr/local/etc/pkgtools.conf to tell portupgrade which options
to use when upgrading a certain port. I
[EMAIL PROTECTED] wrote:
Not in this case. Check /usr/ports/UPDATING 20041107:
: Do NOT use portupgrade(1) to update your GNOME 2.6 desktop to 2.8
Last time this happened, this is what caused my to deinstall gnome. THe upgrade
script could take weeks to run on a reasonable spec machine
From: [EMAIL PROTECTED]
Date: Tue, 07 Dec 2004 17:52:15 +
Sender: [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Not in this case. Check /usr/ports/UPDATING 20041107:
: Do NOT use portupgrade(1) to update your GNOME 2.6 desktop to 2.8
Last time this happened, this is what caused my
As pointed in http://www.freebsd.org/cgi/query-pr.cgi?pr=51970,
is there any driver for the host raid function in the future?
Someone tells me that Linux already has. I guess FreeBSD will do someday.
___
[EMAIL PROTECTED] mailing list
On Tue, 7 Dec 2004, Arjan Van Leeuwen wrote:
On Mon, 6 Dec 2004 19:07:05 -0800 (PST), Doug White
[EMAIL PROTECTED] wrote:
On Mon, 6 Dec 2004, Arjan Van Leeuwen wrote:
(...)
The rate on 'clk' should be 1000, so it looks like your system doesn't
like HZ=1000. Try sticking this in
On Wed, 8 Dec 2004 [EMAIL PROTECTED] wrote:
As pointed in http://www.freebsd.org/cgi/query-pr.cgi?pr=51970,
is there any driver for the host raid function in the future?
Someone tells me that Linux already has. I guess FreeBSD will do someday.
There is no support now, and there is no support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7 Dec 2004, at 18:04, Kevin Oberman wrote:
It seems to me that its a product of gnome being so many ports. Why
not just have a few, like KDE (although it appears KDE is going the
way of gnome - if this results in portupgrade not working there
I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers a
panic, no crashdump is taken although dumps are enabled. What could be
causing this?
rc.conf has
dumpdev=/dev/ad1s3b
dumpdir=/usr/tmp/crash
and ad1s3b is a swap partition with enough space to take a crash dump. I'm
At 09:59 AM 06/12/2004, Ken Smith wrote:
If you are in a position to help with testing and/or debugging for the
upcoming release by all means feel free to begin looking for things
that need to be fixed. However if you are working with a system that
OK, here is another bug that would be nice to
On Tue, Dec 07, 2004 at 05:52:15PM +, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Not in this case. Check /usr/ports/UPDATING 20041107:
: Do NOT use portupgrade(1) to update your GNOME 2.6 desktop to 2.8
Last time this happened, this is what caused my to deinstall gnome. THe
On Tue, Dec 07, 2004 at 05:52:15PM +, [EMAIL PROTECTED] wrote:
It seems to me that its a product of gnome being so many ports. Why
not just have a few, like KDE (although it appears KDE is going the
way of gnome - if this results in portupgrade not working there
either, its insanity).
* With
Gleb Smirnoff wrote:
The patch at
http://people.freebsd.org/~glebius/totest/netgraph_callout
has been updated. Now it covers the following nodes:
ng_bridge.c
ng_l2tp.c
ng_lmi.c
ng_pppoe.c
ng_pptpgre.c
One more time I ask for testing. The patch
On Tuesday, 7. December 2004 23:32, Adam Weinberger wrote:
On Tue, Dec 07, 2004 at 05:52:15PM +, [EMAIL PROTECTED] wrote:
It seems to me that its a product of gnome being so many ports. Why
not just have a few, like KDE (although it appears KDE is going the
way of gnome - if this results
What is this about. I have a error on line 17 on my computer and can't get
into it. Can you help me.
Yvonne
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Tue, Dec 07, 2004 at 07:14:16PM -0500, [EMAIL PROTECTED] wrote:
What is this about. I have a error on line 17 on my computer and can't get
into it. Can you help me.
Not without more information from you. For example: what error, what
version of FreeBSD, what version of the port makefile,
Arjan Van Leeuwen wrote:
Please read the original thread:
http://lists.freebsd.org/mailman/htdig/freebsd-stable/2004-November/009307.html
I couldn't get a crashdump on this machine, but I provided a lot of
information (traces) in that thread.
Since no one replied to my last post in that thread, I
Okay, I know, perhaps not STABLE, but now that 5.3 has become
stable...
Anyway, I have 5.1 installed. I have attempted to buildworld
of 5.2.1, and I get:
=== lib/libpam/modules/pam_deny
cc -O2 -pipe -march=pentiumpro
On Tue, Dec 07, 2004 at 07:40:30PM -0600, Bruce Burden wrote:
=== lib/libpam/modules/pam_deny
cc -O2 -pipe -march=pentiumpro
-I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/openpam/include
-I/usr/src/lib/libpam/modules/pam_deny/../../libpam -Wsystem-headers -Werror
-Wall
not sure if this is the right place to post this ..
i am currently trying to buld a custom kern ( this in an upgrade from 4.9 to
5.3 ) and every time i goto build the kern i get an error saying something is
an unknowen option and now im getting this one and i got this out of
src/UPDATING option
On Tue, Dec 07, 2004 at 06:47:07PM -0800, whitevamp wrote:
not sure if this is the right place to post this ..
i am currently trying to buld a custom kern ( this in an upgrade from 4.9 to
5.3 ) and every time i goto build the kern i get an error saying something is
an unknowen option and now
On Wednesday 08 December 2004 03:57, Kris Kennaway wrote:
On Tue, Dec 07, 2004 at 06:47:07PM -0800, whitevamp wrote:
not sure if this is the right place to post this ..
i am currently trying to buld a custom kern ( this in an upgrade from 4.9
to 5.3 ) and every time i goto build the kern i
On Dec 7, 2004, at 12:38, Wolfgang Zenker wrote:
you can use /usr/local/etc/pkgtools.conf to tell portupgrade which
options
to use when upgrading a certain port. I usually check the makefile of
ports
When using portupgrade(1), are Makefile.local files consulted?
On Wed, Dec 08, 2004 at 04:08:54AM +0100, Max Laier wrote:
On Wednesday 08 December 2004 03:57, Kris Kennaway wrote:
On Tue, Dec 07, 2004 at 06:47:07PM -0800, whitevamp wrote:
not sure if this is the right place to post this ..
i am currently trying to buld a custom kern ( this in an
On Tue, Dec 07, 2004 at 05:50:15PM -0800, Kris Kennaway wrote:
On Tue, Dec 07, 2004 at 07:40:30PM -0600, Bruce Burden wrote:
=== lib/libpam/modules/pam_deny
cc -O2 -pipe -march=pentiumpro
-I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/openpam/include
On Tue, 7 Dec 2004 18:57:13 -0800, Kris Kennaway wrote
On Tue, Dec 07, 2004 at 06:47:07PM -0800, whitevamp wrote:
not sure if this is the right place to post this ..
i am currently trying to buld a custom kern ( this in an upgrade from 4.9 to
5.3 ) and every time i goto build the kern i get
I am unable to install FreeBSD 5.3-RELEASE on my
Soekris net4801, which has a SanDisk Ultra II 512MB
Compact Flash card as a hard drive. The kernel probes
the drive just fine but when it comes time to write or
read from the drive, specifically in sysinstall, I
get;
ad0: TIMEOUT - READ_DMA
37 matches
Mail list logo