Re: Good, stable gigabit nic?

[Markus Trippelsdorf]

On Fri, Oct 07, 2005 at 11:04:23PM -0700, John Pettitt wrote:
> 
> My gigabit nic has gone bad (after months of working just fine  it's
> saying "sk0 watchdog timeout" after a day or so of operation - temp
> fix is to reboot) - I'm looking for pointers for a low cos but
> functional gigabit PCI 32 card that runs under 5.4 without issues.  
> What works for you?

Cards using the RealTek 8169S chipset are cheap (~10 Euro) and are
working without a problem here.
-- 
Markus
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Good, stable gigabit nic?

[John Pettitt]

-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
 


My gigabit nic has gone bad (after months of working just fine  it's
saying "sk0 watchdog timeout" after a day or so of operation - temp
fix is to reboot) - I'm looking for pointers for a low cos but
functional gigabit PCI 32 card that runs under 5.4 without issues.  
What works for you?

John
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (MingW32)
 
iD8DBQFDR2FnaVyA7PElsKkRA+IaAJ9o1AleKkLm/3Dlu+tQtu970bSvOgCfXaFb
zKoGLZlkGFl2UgB5/UjZB3g=
=Si7v
-END PGP SIGNATURE-

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

Re: Stability problems vith FreeBSD 5.2.1-RELEASE-p14

[Adrian Wontroba]

On Sun, Oct 02, 2005 at 07:54:25PM +0200, Jurij Kovacic wrote:
> The panic  message is ussually somewhere along these lines:
> panic: kmem_malloc(4096) kmem map too small: 48496066400 total allocated
> cpuid =0
> boot() called on cpu#0
> ...

A similar problem is described in
http://lists.freebsd.org/pipermail/freebsd-doc/2004-May/004262.html
which recommends setting VM_KMEM_SIZE_MAX 419430400 for machines with
large amounts of memory.

Worked for me on a recent 5-STABLE. Might work for your rather elderly
release.

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

RE: twa kernel panic under heavy IO

[Vinod Kashyap]

> -Original Message-
> From: Brandon Fosdick [mailto:[EMAIL PROTECTED] 
> Sent: Friday, October 07, 2005 6:50 PM
> To: Vinod Kashyap
> Cc: freebsd-stable@freebsd.org; Jung-uk Kim; Dan Rue
> Subject: Re: twa kernel panic under heavy IO
> 
> Vinod Kashyap wrote:
> > Under 'Release Notes to View', select 
> '_Release_Notes_Web', 
> > and you will get to a page which lists the version of each 
> individual 
> > component that's part of the release, among other things.
> 
> :) I would have known that if Firefox wasn't barfing on PDF's 
> right now, or if I had bothered to boot my laptop (OSX).
> 
> The "Release Details" section has a note that reads "Linux 
> and FreeBSD drivers are bundled with firmware 2.08.00.003". 
> What does that mean? Do the drivers in 5-stable have a copy 
> of the firmware embedded in them? Is the driver going to try 
> and downgrade my firmware?
> 

The drivers in the kernel tree are not bundled with the firmware
image by default.  You can bundle them by turning on a switch
in the Makefile.  A bundled driver will download the firmware if
the running firmware is from a different release (9.1*, 9.2* etc.),
or if the running firmware is an older version from the release
corresponding to that of the driver.

> > The 9.2* versions are compatible.  There are small 
> incompatibilities 
> > if you are mixing 9.1* and 9.2*.
> > 
> >>And since we're here...is there any reason to update to 9.3 
> if I only 
> >>have a 9500S?
> 
> Good to know.
> 
> Thanks for the quick reply. FWIW I went with 3ware because I 
> saw somewhere that a 3ware person was supposedly on this 
> list. Glad to see it wasn't a rumor.
> 

You are encouraged to contact 3ware support with questions related
to 3ware.


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and contains information that is 
confidential and proprietary to Applied Micro Circuits Corporation or its 
subsidiaries. It is to be used solely for the purpose of furthering the 
parties' business relationship. All unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: twa kernel panic under heavy IO

[Brandon Fosdick]

Vinod Kashyap wrote:
> Under 'Release Notes to View', select '_Release_Notes_Web',
> and you will get to a page which lists the version of each individual
> component that's part of the release, among other things.

:) I would have known that if Firefox wasn't barfing on PDF's right now, or if 
I had bothered to boot my laptop (OSX).

The "Release Details" section has a note that reads "Linux and FreeBSD drivers 
are bundled with firmware 2.08.00.003". What does that mean? Do the drivers in 
5-stable have a copy of the firmware embedded in them? Is the driver going to 
try and downgrade my firmware?

> The 9.2* versions are compatible.  There are small incompatibilities
> if you are mixing 9.1* and 9.2*.
> 
>>And since we're here...is there any reason to update to 9.3 
>>if I only have a 9500S?

Good to know.

Thanks for the quick reply. FWIW I went with 3ware because I saw somewhere that 
a 3ware person was supposedly on this list. Glad to see it wasn't a rumor.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: twa kernel panic under heavy IO

[Vinod Kashyap]

> -Original Message-
> From: Brandon Fosdick [mailto:[EMAIL PROTECTED] 
> Sent: Friday, October 07, 2005 6:26 PM
> To: Vinod Kashyap
> Cc: freebsd-stable@freebsd.org; Jung-uk Kim; Dan Rue
> Subject: Re: twa kernel panic under heavy IO
> 
> Vinod Kashyap wrote:
> >>How did you figure out the versions? I'm looking at his 
> dmesg, and my 
> >>own, and I'm not seeing the version info in a recognizable form. I 
> >>must admit that I haven't been able to grok the 3ware 
> version numbers 
> >>at all, so maybe I'm dense.
> >>What am I missing?
> > 
> > 
> > 9.1.5.2 and 9.2 are releases from 3ware, of packages of 
> software and 
> > firmware for 9000 series controllers.  The driver version he has 
> > (2.50.02.012) is from the 9.1.5.2 release, and is part of 
> FreeBSD 5.4.  
> > The driver version corresponding to the 9.2 release that's on 5 
> > -STABLE is 3.50.00.017.  You can view/download the 
> different releases 
> > from 3ware on the 3ware website.
> 
> Thanks, that helped. I take it that you just have to know 
> this somehow? Is there a list somewhere that shows the 
> mapping between FreeBSD, driver, and firmware versions?
> 

Under 'Release Notes to View', select '_Release_Notes_Web',
and you will get to a page which lists the version of each individual
component that's part of the release, among other things.

> The 3ware page has 9.2.1.1, which is what I updated to when I 
> installed my 9500, but since then I've cvsup'd to 5-stable. 
> Do I now have mismatched driver-firmware versions? How do I 
> check this in the future? (besides bothering you about it)
> 

The 9.2* versions are compatible.  There are small incompatibilities
if you are mixing 9.1* and 9.2*.
> And since we're here...is there any reason to update to 9.3 
> if I only have a 9500S?
> 

Either way should be fine.

> Thanks
>


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and contains information that is 
confidential and proprietary to Applied Micro Circuits Corporation or its 
subsidiaries. It is to be used solely for the purpose of furthering the 
parties' business relationship. All unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Disable hifn crypto card?

[Brandon Fosdick]

I have a Soekris crypto card (hifn driver) in a box that I don't have immediate 
access to. Is there some way to disable the card w/o rebooting the machine? I 
know I could take the driver out of the kernel or force it not to load, but 
that requires a reboot that I'd like to avoid if possible. hifn is currently 
compiled into the kernel so I can't do a kldunload either. That was the first 
thing I thought of, but apparently today is not my lucky day.

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

Re: twa kernel panic under heavy IO

[Brandon Fosdick]

Vinod Kashyap wrote:
>>How did you figure out the versions? I'm looking at his 
>>dmesg, and my own, and I'm not seeing the version info in a 
>>recognizable form. I must admit that I haven't been able to 
>>grok the 3ware version numbers at all, so maybe I'm dense. 
>>What am I missing?
> 
> 
> 9.1.5.2 and 9.2 are releases from 3ware, of packages of software and
> firmware
> for 9000 series controllers.  The driver version he has (2.50.02.012) is
> from
> the 9.1.5.2 release, and is part of FreeBSD 5.4.  The driver version
> corresponding
> to the 9.2 release that's on 5 -STABLE is 3.50.00.017.  You can
> view/download the different releases from 3ware on the 3ware website.

Thanks, that helped. I take it that you just have to know this somehow? Is 
there a list somewhere that shows the mapping between FreeBSD, driver, and 
firmware versions?

The 3ware page has 9.2.1.1, which is what I updated to when I installed my 
9500, but since then I've cvsup'd to 5-stable. Do I now have mismatched 
driver-firmware versions? How do I check this in the future? (besides bothering 
you about it)

And since we're here...is there any reason to update to 9.3 if I only have a 
9500S?

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

RE: twa kernel panic under heavy IO

[Vinod Kashyap]

> -Original Message-
> From: Brandon Fosdick [mailto:[EMAIL PROTECTED] 
> Sent: Friday, October 07, 2005 6:06 PM
> To: Vinod Kashyap
> Cc: Jung-uk Kim; freebsd-stable@freebsd.org; Dan Rue
> Subject: Re: twa kernel panic under heavy IO
> 
> Vinod Kashyap wrote:
> > Going by the dmesg, you have a 9.1.5.2 driver and 9.2 
> firmware.  The 
> > driver in 5 -STABLE is from the 9.2 release.  So, you might 
> not have 
> > the driver upgrade done properly.  Try using the driver and 
> firmware 
> > from the same release.  If you still see problems, please contact 
> > 3ware support.
> 
> How did you figure out the versions? I'm looking at his 
> dmesg, and my own, and I'm not seeing the version info in a 
> recognizable form. I must admit that I haven't been able to 
> grok the 3ware version numbers at all, so maybe I'm dense. 
> What am I missing?

9.1.5.2 and 9.2 are releases from 3ware, of packages of software and
firmware
for 9000 series controllers.  The driver version he has (2.50.02.012) is
from
the 9.1.5.2 release, and is part of FreeBSD 5.4.  The driver version
corresponding
to the 9.2 release that's on 5 -STABLE is 3.50.00.017.  You can
view/download the different releases from 3ware on the 3ware website.

>


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and contains information that is 
confidential and proprietary to Applied Micro Circuits Corporation or its 
subsidiaries. It is to be used solely for the purpose of furthering the 
parties' business relationship. All unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: twa kernel panic under heavy IO

[Brandon Fosdick]

Vinod Kashyap wrote:
> Going by the dmesg, you have a 9.1.5.2 driver and 9.2 firmware.  The
> driver in 5 -STABLE is from the 9.2 release.  So, you might not have
> the driver upgrade done properly.  Try using the driver and firmware
> from the same release.  If you still see problems, please contact
> 3ware support.

How did you figure out the versions? I'm looking at his dmesg, and my own, and 
I'm not seeing the version info in a recognizable form. I must admit that I 
haven't been able to grok the 3ware version numbers at all, so maybe I'm dense. 
What am I missing?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new FreeBSD-webpage

[jonathan michaels]

greetings all,

my bagage is this .. i am a disabled man who lives with severe
chronicly debiliting pain from significantly danaged neurology and
associated arthritis. there are several other conributing issues but i
don't need to belabour the point more than this.

i use freebsd on hardware that i used to ply my trade (systems analyst
consultant for several organisations involved in the research and
developemt of computer based tools for resource management on broad
acre farm systems and othe niche water resourec management systems and
teh odd scart management systems.

these days i live a leisurely life on a retirement plan otherwise know
as the oinvalide pension .. its meager but its doable enough to keep
body and soul together for the time being.. sortofa grin.

i use lynx browser on an old intel computer, and soon maybe digital
unix on a dec alphastation 255 (with a 233 mhx cpu a 1gb scsi hhd and
128 mb dram and a 10 mhz dec ethernet card) this assumes that i cannot
get freebsd or netbsd installed on this nice little workstation.

i've just tried to spend some time on teh new webpage ...

On Fri, Oct 07, 2005 at 03:12:04PM +1000, Greg Black wrote:
> This belongs on freebsd-www; reply-to set accordingly.
> 
> On 2005-10-06, Kris Kennaway wrote:
> > On Thu, Oct 06, 2005 at 05:37:40PM -0400, Dan Ponte wrote:
> >> On Thu, Oct 06, 2005 at 05:33:26PM -0400, Kris Kennaway <[EMAIL 
> >> PROTECTED]> was witnessed plotting the following conspiracy:
> >>> On Thu, Oct 06, 2005 at 04:43:36PM -0400, Dan Ponte wrote:
> >>> 
>  I second that all the way. Personally, I feel that the FreeBSD project
>  is doing too much in the way of appearing "trendy" to attract new users,
>  and it's at the expense of its existing userbase. Not to mention that
>  the old site rendered perfectly in elinks, while the new one is a mess
>  (scrolling all over the place).
> >>> 
> >>> Thanks for sharing your opinion, but you forgot to explain how a new
> >>> website will make existing FreeBSD users stop using the operating
> >>> system.
> 
> What an absurd way to read what he wrote.  Clearly he meant that
> the reduction in usability of the new site is at the expense of
> the existing userbase which has come to expect certain things
> from the site.  He said nothing about people leaving and you're
> just trolling with the above statement.
> 
> >> I should have worded that differently. By "expense" I didn't mean that
> >> the existing userbase would shrink, but, rather, it would be at a
> >> disadvantage to it. Though, I don't think that anyone would have truly
> >> seen it as the former.
> 
> Nobody who wanted to play fair would have seen it like that.
> 
> > If you think the new design truly puts you at some kind of
> > disadvantage, you should formulate constructive ideas for how to fix
> > that.
> 
> The problems with the new design have been widely canvassed on
> the freebsd-www list, where the discussion belongs.
> 
> Unfortunately, that list is inhabited by a bunch of apologists
> for the new design who seem to be mainly interested in shouting
> down the people who have raised legitimate concerns; or if that
> fails, in belittling them.
> 
> To list the most critical issues:
> 
>   * Many important navigation links (e.g., the Handbook, the
> Ports) disappeared from the front page.
> 
>   * The user interface design is dreadful (e.g., fixed sizes for
> things that cause all kinds of breakage when windows are
> resized or font sizes changed to suit the reader).
> 
>   * Really boring junk has replaced real content on the front
> page (e.g., lengthy list of new committers under the heading
> of "news").
> 
> Anyway, rather than protesting that the new thing is wonderful
> and continually demanding "constructive" criticism from people
> who are offering just that, why not listen to the suggestions
> and see how to improve things?

if i understand this i would like to say yes, please it is time that
freebsd et al lead teh way to show how easy it is to incorporate
daiabled users accability into a large scale generally available
webpage accessed by a wide verity of teh target population.

> 
> For years, I've been sending people to the FreeBSD site to get
> information and help -- universally, I've had excellent feedback
> from all kinds of users about the value and ease of use of the
> site.  The claims that the old site was too hard to use that
> have been advanced as the main reason for the update just don't
> hold water, as far as I'm concerned.

i too have been sending people to teh freebsd web page but unlike
perhaps "gregs people" jonathans crowd have been much like him ..
argumentative, demanding obnoxious opininated and somewhat loudmounted
in thier own ways .. thats teh two leged standing variety, the two
wheeled sitting variety have been just as cantankerious and impossible
to deal with, we as disabled people can be from time to time.
especially when we find webpages that are claimed to be

[releng_6 tinderbox] failure on sparc64/sparc64

[FreeBSD Tinderbox]

TB --- 2005-10-07 23:54:04 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-10-07 23:54:04 - starting RELENG_6 tinderbox run for sparc64/sparc64
TB --- 2005-10-07 23:54:04 - cleaning the object tree
TB --- 2005-10-07 23:54:30 - checking out the source tree
TB --- 2005-10-07 23:54:30 - cd /tinderbox/RELENG_6/sparc64/sparc64
TB --- 2005-10-07 23:54:30 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd 
-rRELENG_6 src
TB --- 2005-10-08 00:04:25 - building world (CFLAGS=-O -pipe)
TB --- 2005-10-08 00:04:25 - cd /src
TB --- 2005-10-08 00:04:25 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
TB --- 2005-10-08 00:52:04 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2005-10-08 00:52:04 - cd /src
TB --- 2005-10-08 00:52:04 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Sat Oct  8 00:52:05 UTC 2005
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=medlow -msoft-float -ffreestanding -Werror 
 /src/sys/dev/random/hash.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=medlow -msoft-float -ffreestanding -Werror 
 /src/sys/dev/random/probe.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=medlow -msoft-float -ffreestanding -Werror 
 /src/sys/dev/random/randomdev.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=medlow -msoft-float -ffreestanding -Werror 
 /src/sys/dev/random/randomdev_soft.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=medlow -msoft-float -ffreestanding -Werror 
 /src/sys/dev/random/yarrow.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpic

[releng_6 tinderbox] failure on i386/pc98

[FreeBSD Tinderbox]

TB --- 2005-10-07 22:51:45 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-10-07 22:51:45 - starting RELENG_6 tinderbox run for i386/pc98
TB --- 2005-10-07 22:51:45 - cleaning the object tree
TB --- 2005-10-07 22:52:07 - checking out the source tree
TB --- 2005-10-07 22:52:07 - cd /tinderbox/RELENG_6/i386/pc98
TB --- 2005-10-07 22:52:07 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd 
-rRELENG_6 src
TB --- 2005-10-07 23:01:43 - building world (CFLAGS=-O -pipe)
TB --- 2005-10-07 23:01:43 - cd /src
TB --- 2005-10-07 23:01:43 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
TB --- 2005-10-07 23:50:46 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2005-10-07 23:50:46 - cd /src
TB --- 2005-10-07 23:50:46 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Fri Oct  7 23:50:46 UTC 2005
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/hash.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/probe.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/randomdev.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/randomdev_soft.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-

[releng_6 tinderbox] failure on i386/i386

[FreeBSD Tinderbox]

TB --- 2005-10-07 21:47:54 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-10-07 21:47:54 - starting RELENG_6 tinderbox run for i386/i386
TB --- 2005-10-07 21:47:54 - cleaning the object tree
TB --- 2005-10-07 21:48:24 - checking out the source tree
TB --- 2005-10-07 21:48:24 - cd /tinderbox/RELENG_6/i386/i386
TB --- 2005-10-07 21:48:24 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd 
-rRELENG_6 src
TB --- 2005-10-07 21:58:07 - building world (CFLAGS=-O -pipe)
TB --- 2005-10-07 21:58:07 - cd /src
TB --- 2005-10-07 21:58:07 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
TB --- 2005-10-07 22:47:31 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2005-10-07 22:47:31 - cd /src
TB --- 2005-10-07 22:47:31 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Fri Oct  7 22:47:32 UTC 2005
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/hash.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/probe.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/randomdev.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 
-ffreestanding -Werror  /src/sys/dev/random/randomdev_soft.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-

[releng_6 tinderbox] failure on amd64/amd64

[FreeBSD Tinderbox]

TB --- 2005-10-07 20:22:00 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-10-07 20:22:00 - starting RELENG_6 tinderbox run for amd64/amd64
TB --- 2005-10-07 20:22:00 - cleaning the object tree
TB --- 2005-10-07 20:22:40 - checking out the source tree
TB --- 2005-10-07 20:22:40 - cd /tinderbox/RELENG_6/amd64/amd64
TB --- 2005-10-07 20:22:40 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd 
-rRELENG_6 src
TB --- 2005-10-07 20:32:12 - building world (CFLAGS=-O -pipe)
TB --- 2005-10-07 20:32:12 - cd /src
TB --- 2005-10-07 20:32:12 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
>>> stage 5.1: building 32 bit shim libraries
TB --- 2005-10-07 21:43:32 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2005-10-07 21:43:32 - cd /src
TB --- 2005-10-07 21:43:32 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Fri Oct  7 21:43:32 UTC 2005
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=kernel -mno-red-zone  -mfpmath=387 
-mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -Werror  
/src/sys/dev/random/hash.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=kernel -mno-red-zone  -mfpmath=387 
-mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -Werror  
/src/sys/dev/random/probe.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=kernel -mno-red-zone  -mfpmath=387 
-mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -Werror  
/src/sys/dev/random/randomdev.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mcmodel=kernel -mno-red-zone  -mfpmath=387 
-mno-sse -mno-sse2 -mno-mmx -mno-3dnow  -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -Werror  
/src/sys/dev/random/randomdev_soft.c
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
-std=c99 -g -nostdinc -I-  -I. -I/src/sys -I/src/sys/contrib/dev/acpica 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf 
-I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL 
-DHAVE_KERNEL_OPTION_HE

Re: new FreeBSD-webpage

[jdow]

From: "Garance A Drosehn" <[EMAIL PROTECTED]>


At 3:42 PM -0700 10/6/05, Murray Stokely wrote:

On Thu, Oct 06, 2005, Dan Ponte wrote:
 > One idea is to revert to the old design, which suited people's
 > needs just fine. However, I doubt that will happen.

Uhm, it didn't suit people's needs just fine.  It was total crap
with dozens of disorganized links all over the front page and
second level pages topping 100k as they had just grown larger
and larger over time and noone had stepped back to look at how
bad it all was for someone coming to the site for the first
time to find any useful information.


I agree with Murray.  I'm sure the new design can be improved upon
some more, but the previous web pages had gotten to the point that
they actively annoyed me.  Too large, too much info crammed into
some of the pages.  I have been saving URL's directly to some inner
web pages, for no other reason than to avoid bringing up the main
web page.  And once you're AVOIDING the web page, then it doesn't
much matter how much info was crammed into it.


As a newbie (to FreeBSD not to 'nix) I found the older pages had the
information more accessible than the newer pages, which I rather
involuntarily had the opportunity to A/B test when I was installing
FreeBSD for the first time. Between FreeBSD coming up actively user
hostile (DECUS UNIX from 197x was no worse) and the web page changes
t became a challenge to find the documentation pages I needed to work
with.

I also disable font size selection on the browsers I use. I have a
large screen. I like to sit comfortably back and use large fonts
to lose the "dottiness" of 8 dot high fonts such as many of the
news service and blog pages use. This makes fixed size pages all
neatly calibrated in pixels look like  warmed over
twice. Pages that adapt to reality are much nicer.

With regards to the rather spartan new front page I note that while
I was setting up 5.4-RELEASE I also noted that there was a 6 in test
and had filed that for investigation once I got basic essentials more
or less working. When I went back to do that I had to mouse around for
10 minutes before I found 6-CURRENT was what that former link had been
about. (In the mean time I found 7-CURRENT with no references to
6-CURRENT. I mumbled to myself, "WTH, FreeBSD is doing marketdroid
tricks with version numbers? Can't be!")

So for what it is worth this is the reaction of a newbie (but only to
BSD rather than DECUS, SVR4, and Linux) who faced an involuntary A/B
test. I much prefer the old first page, although I cannot say I was
hugely in love with it. As observed it was a little busy. But over
compensation is not a correct response to "a little". It's line you
moved 20 dB when 1 dB would have been sufficient.

{^_^}Joanne

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

[releng_6 tinderbox] failure on alpha/alpha

[FreeBSD Tinderbox]

TB --- 2005-10-07 19:15:00 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-10-07 19:15:00 - starting RELENG_6 tinderbox run for alpha/alpha
TB --- 2005-10-07 19:15:00 - cleaning the object tree
TB --- 2005-10-07 19:15:29 - checking out the source tree
TB --- 2005-10-07 19:15:29 - cd /tinderbox/RELENG_6/alpha/alpha
TB --- 2005-10-07 19:15:29 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd 
-rRELENG_6 src
TB --- 2005-10-07 19:25:14 - building world (CFLAGS=-O -pipe)
TB --- 2005-10-07 19:25:14 - cd /src
TB --- 2005-10-07 19:25:14 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
TB --- 2005-10-07 20:13:14 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2005-10-07 20:13:14 - cd /src
TB --- 2005-10-07 20:13:14 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Fri Oct  7 20:13:14 UTC 2005
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
touch export_syms
awk -f /src/sys/modules/rc4/../../conf/kmod_syms.awk rc4.kld  export_syms | 
xargs -J% objcopy % rc4.kld
ld -Bshareable  -d -warn-common -o rc4.ko.debug rc4.kld
objcopy --strip-debug rc4.ko.debug rc4.ko
===> re (all)
cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Werror -D_KERNEL -DKLD_MODULE 
-nostdinc -I-   -DHAVE_KERNEL_OPTION_HEADERS -include 
/obj/alpha/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include 
-finline-limit=15000 -fno-common -g -I/obj/alpha/src/sys/GENERIC -mno-fp-regs 
-ffixed-8 -Wa,-mev6 -ffreestanding -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -c /src/sys/modules/re/../../dev/re/if_re.c
/src/sys/modules/re/../../dev/re/if_re.c: In function `re_ioctl':
/src/sys/modules/re/../../dev/re/if_re.c:2286: warning: 'error' might be used 
uninitialized in this function
*** Error code 1

Stop in /src/sys/modules/re.
*** Error code 1

Stop in /src/sys/modules.
*** Error code 1

Stop in /obj/alpha/src/sys/GENERIC.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2005-10-07 20:21:59 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2005-10-07 20:21:59 - ERROR: failed to build generic kernel
TB --- 2005-10-07 20:21:59 - tinderbox aborted

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

5.4 hangs on disk IO

[Douglas K. Rand]

I've got 2 FreeBSD 5.4 systems that seem to get stuck doing disk
IO. When the system gets hung, it seems to refuse to do any disk
io. It will continue to respond to pings, and the tty driver on the
serial console continues to work and echo characters. But all the
processes seem to get stuck in the state "ufs". On the serial console
I tried sync, which then hangs, and ^T produces:

athearn# sync
load: 0.66  cmd: csh 4138 [ufs] 0.00u 0.00s 0% 1748k

One of the systems emits these error messages on the console:

swap_pager: indefinite wait buffer: device: da0s1a, blkno: 2, size: 4096
swap_pager: indefinite wait buffer: device: da0s1h, blkno: 6, size: 4096
swap_pager: indefinite wait buffer: device: da0s1h, blkno: 7, size: 4096
swap_pager: indefinite wait buffer: device: da0s1h, blkno: 15, size: 4096
swap_pager: indefinite wait buffer: device: da0s1a, blkno: 26, size: 4096

Other than that difference, both systems hang the same way.

The interesting part is that it only seems to happen when I run
amd. With amd running one of our users can hang the system in about
5-10 minutes of heavy disk traffic to a LOCAL disk. The local disk
with the heaviest traffic is "behind" a amd managed symlink. If I
don't run amd and do all the NFS mounts by hand and build the symlink
by hand, the system runs fine. I've tried both the stock amd that
comes with 5.4, the fairly outdated 6.0.10-20040513, and the brand new
6.1.2.1 from ports. 

From the kernel debugger I can't even panic or call boot(0) with out
errors. 

I can easily reproduce the hang, so if there is any suggestions for
things to poke at with the kernel debugger on the serial console, let
me know.

Here's the result of ps from a hung system, along with the errors from
panic and boot(0):

db> ps
  pid   proc uid  ppid  pgrp  flag   stat  wmesgwchan  cmd
 4138 c34051c40   530  4138 412 [SLPQ ufs 0xc346b2bc][SLP] csh
 4137 c3e8be20 1002   740   735 400 [SLPQ sbwait 0xc366fe84][SLP] perl5.8.7
 4136 c3e8bc5c 1002   741   735 400 [SLPQ sbwait 0xc3a95d40][SLP] perl5.8.7
 4135 c3e071c4 1002   743   735 0004000 [SLPQ nfs 0xc35a7e14][SLP] mkdir
 4134 c3d8e1c4 1002   749   735 0004000 [SLPQ ufs 0xc346b2bc][SLP] perl5.8.7
 4132 c3e6154c 1002   739   735 0004000 [SLPQ nfs 0xc35a7e14][SLP] remap
 2355 c3714a98 1000   682  2355 0004002 [SLPQ select 0xc06787c4][SLP] top
  749 c3ba3c5c 1002 1   735 0004002 [SLPQ wait 0xc3ba3c5c][SLP] tclsh8.4
  748 c348f54c 1002 1   735 0004002 [SLPQ accept 0xc36a6a5a][SLP] perl5.8.7
  747 c3710a98 1002 1   735 0004002 [SLPQ accept 0xc3a6154a][SLP] perl5.8.7
  746 c370fa98 1002 1   735 0004002 [SLPQ accept 0xc374e17e][SLP] perl5.8.7
  745 c3ba3e20 1002 1   735 0004002 [SLPQ accept 0xc374e68e][SLP] perl5.8.7
  744 c3ba6000 1002 1   735 0004002 [SLPQ accept 0xc35ac7d2][SLP] perl5.8.7
  743 c3ba61c4 1002 1   735 0004002 [SLPQ wait 0xc3ba61c4][SLP] perl5.8.7
  742 c3ba6388 1002 1   735 0004002 [SLPQ accept 0xc366f406][SLP] perl5.8.7
  741 c34b6e20 1002 1   735 0004002 [SLPQ wait 0xc34b6e20][SLP] perl5.8.7
  740 c34b6388 1002 1   735 0004002 [SLPQ wait 0xc34b6388][SLP] perl5.8.7
  739 c34b6c5c 1002 1   735 0004002 [SLPQ wait 0xc34b6c5c][SLP] perl5.8.7
  682 c34ef000 1000   681   682 0004002 [SLPQ pause 0xc34ef038][SLP] zsh
  681 c340954c 1000   678   678 100 [SLPQ select 0xc06787c4][SLP] sshd
  678 c348ca980   442   678 100 [SLPQ sbwait 0xc3a616ec][SLP] sshd
  530 c3710e200   529   530 0004002 [SLPQ ppwait 0xc3710e20][SLP] csh
  529 c370f3880 1   529 0004102 [SLPQ wait 0xc370f388][SLP] login
  528 c37103880 1   528 0004002 [SLPQ ttyin 0xc31d0a10][SLP] getty
  527 c348c1c40 1   527 0004002 [SLPQ ttyin 0xc31b8410][SLP] getty
  526 c348f3880 1   526 0004002 [SLPQ ttyin 0xc31b8010][SLP] getty
  525 c34ef8d40 1   525 0004002 [SLPQ ttyin 0xc3166c10][SLP] getty
  524 c34b6a980 1   524 0004002 [SLPQ ttyin 0xc3166210][SLP] getty
  523 c348f8d40 1   523 0004002 [SLPQ ttyin 0xc3166410][SLP] getty
  522 c348ce200 1   522 0004002 [SLPQ ttyin 0xc3166610][SLP] getty
  521 c34f3e200 1   521 0004002 [SLPQ ttyin 0xc3166810][SLP] getty
  491 c34053880 1   490 000 [SLPQ ufs 0xc346b2bc][SLP] snmpd
  464 c37107100 1   464 000 [SLPQ ufs 0xc346b2bc][SLP] cron
  452 c34b6710   25 1   452 100 [SLPQ pause 0xc34b6748][SLP] sendmail
  448 c37140000 1   448 100 [SLPQ pause 0xc3714038][SLP] sendmail
  442 c34f38d40 1   442 100 [SLPQ select 0xc06787c4][SLP] sshd
  427 c34097100 1   427 000 [SLPQ select 0xc06787c4][SLP] ntpd
  382 c3167c5c0   378   378 000 [SLPQ - 0xc3383c00][SLP] nfsd
  381 c34ef3880   378   378 000 [SLPQ - 0xc33d7200][SLP] nfsd
  380 c34f354c0   378   378 000 [SLPQ - 0xc33f6400][SLP] nfsd
  379 c34b654c0   378   378 000 [SLPQ - 0xc338f000][SLP] nfsd
  378 c34057100 1   378 000 [SLPQ accept 0xc365403a][SLP] 

Re: new FreeBSD-webpage

[Garance A Drosehn]

At 3:42 PM -0700 10/6/05, Murray Stokely wrote:

On Thu, Oct 06, 2005, Dan Ponte wrote:
 > One idea is to revert to the old design, which suited people's
 > needs just fine. However, I doubt that will happen.

Uhm, it didn't suit people's needs just fine.  It was total crap
with dozens of disorganized links all over the front page and
second level pages topping 100k as they had just grown larger
and larger over time and noone had stepped back to look at how
bad it all was for someone coming to the site for the first
time to find any useful information.


I agree with Murray.  I'm sure the new design can be improved upon
some more, but the previous web pages had gotten to the point that
they actively annoyed me.  Too large, too much info crammed into
some of the pages.  I have been saving URL's directly to some inner
web pages, for no other reason than to avoid bringing up the main
web page.  And once you're AVOIDING the web page, then it doesn't
much matter how much info was crammed into it.

--
Garance Alistair Drosehn =  [EMAIL PROTECTED]
Senior Systems Programmer   or   [EMAIL PROTECTED]
Rensselaer Polytechnic Institute; Troy, NY;  USA
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new FreeBSD-webpage

[Brad Knowles]

At 7:04 PM +0200 2005-10-07, Oliver Fromme wrote:


  > Scrolling is always preferable to clicking since it requires less
  > effort and has a better response time.

 I'm afraid I have to disagree.  Moving the mouse pointer to
 the scroll bar, clicking it and dragging it is definitely
 more effort than simply clicking a link.


	It depends on how much bandwidth you have, and how bad the 
latency is between you and the web server response.  If you have 
infinite bandwidth and the latency is virtually zero, then clicking a 
link is faster.  If you have lower bandwidth and/or higher latency, 
then scrolling is likely to be better.


Who are you going to try to optimize the web pages for?

--
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755

  SAGE member since 1995.  See  for more info.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

error building re-module

[Claus Guttesen]

>From make buildkernel from RELENG_6 as of Oct. 7'th 20:00 GMT:

===> re (all)
cc -O2 -pipe -march=athlon64 -fno-strict-aliasing -Werror -D_KERNEL
-DKLD_MODULE -nostdinc -I-   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/TWIN/opt_global.h -I. -I@ -I@/contrib/altq
-I@/../include -finline-limit=8000 -fno-common -g
-fno-omit-frame-pointer -I/usr/obj/usr/src/sys/TWIN -mcmodel=kernel
-mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow 
-msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual 
-fformat-extensions -std=c99 -c
/usr/src/sys/modules/re/../../dev/re/if_re.c
/usr/src/sys/modules/re/../../dev/re/if_re.c: In function `re_ioctl':
/usr/src/sys/modules/re/../../dev/re/if_re.c:2286: warning: 'error'
might be used uninitialized in this function
*** Error code 1

Stop in /usr/src/sys/modules/re.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/TWIN.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

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

Re: new FreeBSD-webpage

[Oliver Fromme]

Tuomo Latto <[EMAIL PROTECTED]> wrote:
 > Greg Barniskis wrote:
 > > well, usability is not an entirely objective measure, but there are 
 > > objective aspects to it. Like, not having to scroll to find crucial 
 > > navigation links and the Search box, or to see what the latest 
 > 
 > You forget the number 1 rule:
 > Thou shalt not add to the number of clicks required.
 > 
 > Scrolling is always preferable to clicking since it requires less
 > effort and has a better response time.

I'm afraid I have to disagree.  Moving the mouse pointer to
the scroll bar, clicking it and dragging it is definitely
more effort than simply clicking a link.

(And don't tell me everyone has a mouse with a scroll wheel.
That assumption would be wrong.)

 > So, here's a specific and constructive suggestion:
 > Add on a clearly visible place on the front page a link pointing
 > to the old site and keep the old site updated as well.
 > How about "Not new to FreeBSD?" under the "New to FreeBSD?"?

I would rather suggest to remove the old page as soon as
possible, before people are starting to create hyper links
to it.  The longer the old front page is available, the
bigger the problem will grow.

 > Here's another: Make all headings links.

That's a good idea.

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

Python is executable pseudocode.  Perl is executable line noise.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Switching from RELENG_4 to newer Release that supports ia64

[Brooks Davis]

On Fri, Oct 07, 2005 at 12:36:13PM +0200, Michael Schuh wrote:
> Hello,
> 
> we plan to change the Hardware from one of our Servers Running RELENG_4.
> The New Hardware becomes CPU-Types Xeon w/ EM64 -> ia64 architecture.
>
> Now i have no experiences to change the OS-Release under the ass
> from running Software (postfix/cyrus/postgresql/mysql/perletc.)

Xeons with EM64T are amd64 architecture.  I very much doubt you are
switching to ia64, particularly for a mail/db/web server.

> I be also not sure what release-version should i take.
> 
> My preferred opinion was to change to the upcoming RELENG_6,
> but i be not sure if this is really a good idea, second i have no
> documents found to migrate from RELENG_4 to RELENG_6.
>
> I know it gives a very good description of changing the underlying
> OS-Version to RELENG_5.

I'd choose 6.0 over 5.4 at this point.  Since you are changing to new
hardware, you will definitly want to reinstall and reconfigure your
services (you can of course use your old configurations.)

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgp9F8sSSLJRY.pgp
Description: PGP signature

Re: setsockopt and SO_RCV/SNDTIMEO

[Chuck Swiger]

Gleb Smirnoff wrote:

On Fri, Oct 07, 2005 at 05:04:40PM +0300, Lefteris Tsintjelis wrote:
L> >You are expecting wrong from these socket options. They do not specify
L> >time after which socket should be closed, if no IO is done.
L> 
L> Is there any easy build in functionality for that?


Pardon, but I do not understand the question.


He wants the connection to be closed after a certain number of seconds if it is 
idle.


Lefterius, when you read() from the socket, call time().  If you read more than 
zero bytes, save that time in a variable.  If you read zero bytes, compare what 
time it is now to the saved value, and if the delta is greater than when you 
want an idle connection to close, well, call close() and exit or whatever.


Details like initializing the variable to now beforehand are probably needed.

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

Re: new FreeBSD-webpage

[Marian Hettwer]

Hej Dave,

Dave Fazio wrote:
Totally agree and understand your point -- a graphical install option 
would mainly appeal to desktop users.  But let's be honest; considering 
the competition install base of  Red Hat, Mac OS X, SUN, and (ech!) 
Windows, the day of GUI deskop'd servers is here now; Purests hate it 
Well, RedHat has a graphical installer, but redhat also has a tool 
called kickstart for automatic installations. So they have basically both :)

Sun has something similar for Solaris, I forgot the name, though.

sure, but it's a fact, and shouldn't be discounted altogether as an 
option for modern day server configurations.


should be IMO still non-graphical as long as you have big serverfarms 
like Database and Webservers. I'm managing approx 1000 servers with some 
colluegues. Unluckily it's Debian GNU/Linux systems, but at least it's 
an automatic installation done via FAI (google for FAI Debian).
I'd prefer FreeBSD, though. And I know that there are some tutorials 
howto do an automagic installation of FreeBSD.



There's no point to digress more on this subject now, but FreeBSD is in 
my opinion the best of *all* general purpose OSs -- But to properly 
manage a FreeBSD (ports/packages,source builds, etc), the devil is 
definitely in the details.  Apple has smoothed our these details in 
short order -- why can't we?
I don't know about MacOS X as a server. I'm just using it on my 
PowerBook for daily work :)


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

Re: setsockopt and SO_RCV/SNDTIMEO

[Lefteris Tsintjelis]

Gleb Smirnoff wrote:

On Fri, Oct 07, 2005 at 05:04:40PM +0300, Lefteris Tsintjelis wrote:
L> >You are expecting wrong from these socket options. They do not specify
L> >time after which socket should be closed, if no IO is done.
L> 
L> Is there any easy build in functionality for that?


Pardon, but I do not understand the question.


Is there any easy way to setup IO timeouts (read/write) for a socket to
close in case of inactivity?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new FreeBSD-webpage

[Bob Johnson]

On 10/6/05, Bartosz Fabianowski <[EMAIL PROTECTED]> wrote:
> > monitor are wider than taller, why restrain horizontal space ?
>
> A fixed width design is very fashionable these days and you see it creeping
> up everywhere. It's what's considered "professional" these days, so I can't
> really blame anybody trying to appear professional for choosing it. But I
> still think that this is a bad trend. On my wide screen laptop, 50% of the
> screen are wasted blank space.

Fixed width designs are popular with graphic artists because they can
force everything to look exactly the way they want it.  On their
monitor.  With their browser.  For those of us that don't use exactly
the same display resolution or browser (and fonts), the result is
usually disappointing at best.  The new site looks like #$^% and is
very difficult to use, for example, on a PDA with Pocket Internet
Explorer.

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

Get yourself back on track today!

[Josephine Roach]

One stop store for best levitra buy.
http://kymzr.1a63p5plpgo91jjc61jcojj1.mazalgiabi.com/?cajdka


Moral victories don't count. 
Eternity is a mere moment, just long enough for a joke.  
We only do well the things we like doing.

Jealousy is all the fun you think they had.
Too many pieces of music finish too long after the end.  
Not many people know this ... but I happen to be famous. 
If you have a job without aggravations, you don't have a job. 

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

Re: setsockopt and SO_RCV/SNDTIMEO

[Gleb Smirnoff]

On Fri, Oct 07, 2005 at 05:04:40PM +0300, Lefteris Tsintjelis wrote:
L> >You are expecting wrong from these socket options. They do not specify
L> >time after which socket should be closed, if no IO is done.
L> 
L> Is there any easy build in functionality for that?

Pardon, but I do not understand the question.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: setsockopt and SO_RCV/SNDTIMEO

[Lefteris Tsintjelis]

Gleb Smirnoff wrote:


You are expecting wrong from these socket options. They do not specify
time after which socket should be closed, if no IO is done.


Is there any easy build in functionality for that?

Thnx,

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

Re: new FreeBSD-webpage

[Jamie Heckford]

Would just like to say I think the new site looks great, well done and 
thanks to all the people that have donated spare time to work on this.


Maybe all the moaning minnies would like to submit a URL where they have 
put hardwork into making an alternative site for us all to see, instead 
of poking at the current one.

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

Re: ipfw: firewall.sh don't work!

[Chris]

On Fri, 7 Oct 2005,   wrote:


Hi all!
FreeBSD 5.4 p7.

ipfw works in a mode - firewall_type="open" only.
At attempt to apply firewall_script="/etc/firewall.sh" the system
forbids the traffic even if firewall.sh configured as "allow all any to
any"

my kernel:
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100
options IPFIREWALL_FORWARD
options IPFIREWALL_FORWARD_EXTENDED
options IPDIVERT
options DUMMYNET

rc.conf:
gateway_enable="YES"
ifconfig_bge0="inet 192.168.1.1"
ifconfig_xl0="inet ..."
icmp_drop_redirect="YES"
icmp_log_redirect="YES"
icmp_bmcastecho="NO"
firewall_enable="YES"
#firewall_type="OPEN"
firewall_script="/etc/firewall.sh"
firewall_logging="YES"
natd_enable="YES"
natd_interface="xl0"
natd_flags="-s"

/etc/firewall.sh:
#!/bin/sh

ipfw='/sbin/ipfw -q'
inet='xl0'
lan='bge0'

${ipfw} -a flush
${ipfw} add 100 allow all from any to any via lo0


${ipfw} add 300 divert natd tcp from any to any via ${inet}
${ipfw} add 310 divert natd udp from any to any via ${inet}

${ipfw} add 400 deny icmp from any to any in icmptype
5,9,13,14,15,16,17
${ipfw} add 410 deny icmp from any to any frag
${ipfw} add 420 allow icmp from any to any
${ipfw} add 500 deny tcp from any to 192.168.1.0/24 137-139 via ${inet}
${ipfw} add 510 deny udp from any to 192.168.1.0/24 137-139 via ${inet}
${ipfw} add 520 deny ip from 192.168.1.0/24 to any in via ${inet}
${ipfw} add 530 allow tcp from 192.168.1.1 to any 5999
${ipfw} add 540 allow udp from any 53 to any
${ipfw} add 550 allow udp from any to any 53

${ipfw} add 600 allow tcp from 192.168.1.0/24 to any
20,21,25,80,110,443,5190
${ipfw} add 610 allow tcp from any 20,21,25,80,110,443,5190 to
192.168.1.0/24

where a problem?
thanks!


Go back to the HAndbook and read it again. You'll see that you are NOT 
making the proper references for LAN traffic and internet traffic.



Best regards,
Chris

A little ambiguity never hurt anyone.___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ipfw: firewall.sh don't work!

[Горсткин Илья]

Hi all!
FreeBSD 5.4 p7.

ipfw works in a mode - firewall_type="open" only.
At attempt to apply firewall_script="/etc/firewall.sh" the system
forbids the traffic even if firewall.sh configured as "allow all any to
any"

my kernel:
options IPFIREWALL 
options IPFIREWALL_VERBOSE 
options IPFIREWALL_VERBOSE_LIMIT=100 
options IPFIREWALL_FORWARD 
options IPFIREWALL_FORWARD_EXTENDED 
options IPDIVERT 
options DUMMYNET

rc.conf:
gateway_enable="YES"
ifconfig_bge0="inet 192.168.1.1"
ifconfig_xl0="inet ..."
icmp_drop_redirect="YES" 
icmp_log_redirect="YES" 
icmp_bmcastecho="NO"  
firewall_enable="YES"
#firewall_type="OPEN" 
firewall_script="/etc/firewall.sh" 
firewall_logging="YES" 
natd_enable="YES" 
natd_interface="xl0" 
natd_flags="-s"

/etc/firewall.sh:
#!/bin/sh 

ipfw='/sbin/ipfw -q' 
inet='xl0' 
lan='bge0' 

${ipfw} -a flush 
${ipfw} add 100 allow all from any to any via lo0   


${ipfw} add 300 divert natd tcp from any to any via ${inet} 
${ipfw} add 310 divert natd udp from any to any via ${inet} 

${ipfw} add 400 deny icmp from any to any in icmptype
5,9,13,14,15,16,17 
${ipfw} add 410 deny icmp from any to any frag 
${ipfw} add 420 allow icmp from any to any 
${ipfw} add 500 deny tcp from any to 192.168.1.0/24 137-139 via ${inet} 
${ipfw} add 510 deny udp from any to 192.168.1.0/24 137-139 via ${inet} 
${ipfw} add 520 deny ip from 192.168.1.0/24 to any in via ${inet} 
${ipfw} add 530 allow tcp from 192.168.1.1 to any 5999 
${ipfw} add 540 allow udp from any 53 to any 
${ipfw} add 550 allow udp from any to any 53 

${ipfw} add 600 allow tcp from 192.168.1.0/24 to any
20,21,25,80,110,443,5190 
${ipfw} add 610 allow tcp from any 20,21,25,80,110,443,5190 to
192.168.1.0/24

where a problem?
thanks!

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

Re: new FreeBSD-webpage

[Tuomo Latto]

Miguel Saturnino wrote:
>>You'd expect popups from the links on the top (they look like that
>>sort of links), but none seem to appear and I've just wasted time
>>waiting for them to appear.
> 
> Why would you expect pop-up windows from the new menu? Why does this
> menu looks like a menu that will pop up a new window? To me, it just
> looks like a nice menu -- and I certainly don't expect pop-up windows
> from it.

Ah, I can see you're one of the lucky ones to have missed certain
corporate sites. Most of them seem to provide a look and an interface
just like this one. Mainly the idea is to make the corporation look
business-like. The actual content (or whatever part of it that is
of any use) is hidden somewhere beneath in order to discourage people
from reading it too closely.

To me, this sort of design just means "we want to be boring, not care
and just be like everyone else" instead of conveying a sense of
originality and passion to their work. But maybe that's just me.


>>With Opera, about 40% of the screen space is left unused.
>>I *liked* the quick links the old one had on the sides.
> 
> If you try it with a screen resolution of 800x600 it will fill all the
> screen ;) A fluid design can be more usable in different screen
> resolutions, but when you want something prettier you need to restrain
> the horizontal width to get a consistent look across different screen
> resolutions. Almost every site (with fixed width) restrains the width to
> less than 800 pixels so that users with an 800x600 resolution don't need
> to scroll horizontally.

So because other sites do it it's ok here too?
And *I'm* supposed to provide constructive feedback..?


> To me, the new site looks nicer than the old one, and I'm pretty sure
> most people (specially and more importantly new visitors) will find it
> more attractive than the old one!

I agree that some people may find it more attractive. I don't.

The major problem in my view is the functionality.
A lot of information has been hidden, the existence of scroll bars
has been forgotten and so on..
I don't want horizontal scrolling, but vertical is tried and true.
It is known that it works.

The expression that comes to mind is dumbing down - and not in a good way.


-- 
Tuomo

... I'm fat. You're ugly. I can diet.

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

Re: new FreeBSD-webpage

[Tuomo Latto]

Greg Barniskis wrote:
> Dan Ponte wrote:
>>>I doubt the primary goal here
>>>was to appear trendy.
>>
>>Well, it certainly seems as if that was one of the goals, seeing how the
>>new site uses quite a few new webdesign concepts that came into
>>existence in the past few years, while providing little benefit in the
>>way of content or usability.
> 
> well, usability is not an entirely objective measure, but there are 
> objective aspects to it. Like, not having to scroll to find crucial 
> navigation links and the Search box, or to see what the latest 

You forget the number 1 rule:
Thou shalt not add to the number of clicks required.

Scrolling is always preferable to clicking since it requires less
effort and has a better response time.


> security advisory was. Like, reducing 20-30 headings in big "stacks" 
> to clearly bounded clusters of "7 +/- 2", fostering rapid 
> understanding. I think usability is measurably up.

Reducing headings in clearly defined sections to less clearly
defined links improves usability?


> I suppose in sense it does break down in a way that the old site was 
> "more usable" for experts (usable once one had studied on it awhile, 
> that is), while the new layout might be more usable for newbies. But 
> that doesn't mean it was "for newbies". I like it, and I've been 
> poking at the web site for a decade now. I was put off for maybe 15 
> secs the first time I looked at it, then I started to accept and 
> appreciate (aw, who can resist that big smilin' Beastie ;).

I like the beastie too. But that's about it.


> It's got some quirks. I'm seeing some more things suffer from fixed 
> widths (and fixed heights, like the mirror selector widget -- px is 
> just not the most user-friendly unit of measure), but the path it's 
> on seems a good one. Like Kris said, if you've got a specific 
> problem, constructively suggest a specific solution (other than just 
> reverting).

I see now that the powers that be have already decided that this
is the way of the future (good grief). I see it in the comments
to peoples' reactions and in the way the whole thing was planned
in relative secrecy and then just dropped on the rest of us.
I suppose I should at least try to minimize the damage on my behalf.

So, here's a specific and constructive suggestion:
Add on a clearly visible place on the front page a link pointing
to the old site and keep the old site updated as well.
How about "Not new to FreeBSD?" under the "New to FreeBSD?"?


Here's another: Make all headings links.
If I want to see all security advisories, I don't want to have to search
for that little "More". Instead, I'd prefer to click on the heading and
get the security advisory page.

But where are the advisories on that page? Oh, *now* I have to scroll..
That table of contents is squeezed between the introduction and
the rest of the content. It is customary to have table of contents first
so people can actually umm.. you know.. find it.


-- 
Tuomo

... I am willing to make the mistakes if someone else is willing to
learn from them
-- Ways for Personal Growth
   http://www.ericbair.com/humor/PerGrowth.txt

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

Re: new FreeBSD-webpage

[Simon L. Nielsen]

[Redirected to -www since that's where stuff about the web page should
be discussed, not -stable]

On 2005.10.06 21:17:50 +1000, Peter Jeremy wrote:

> I'd suggest that the most important feature that is missing is a
> website map.  The website looks nothing like it used to and many of my
> commonly referenced links are no longer on the home page.  Finding my
> way around is going to be very time consuming until I learn my way
> around it.

That sounds like a good idea.  We have
http://www.freebsd.org/search/index-site.html but it's in need of an
update, and probably some place more visible to be linked from.

> On the positive side, I'm glad that it's still usable with a text
> browser.

IMO actually even more than before.

> On the downside, I notice it now uses cookies.

AFAIR (I haven't double checked) it uses a cookie to remember if you
choose normal or large font - it's not required.

-- 
Simon L. Nielsen


pgp75US14SKaC.pgp
Description: PGP signature

Re: new FreeBSD-webpage

[Marwan Burelle]

On Fri, Oct 07, 2005 at 10:21:44AM +0100, Miguel Saturnino wrote:
> > With Opera, about 40% of the screen space is left unused.
> > I *liked* the quick links the old one had on the sides.
> 
> If you try it with a screen resolution of 800x600 it will fill all the
> screen ;) A fluid design can be more usable in different screen
> resolutions, but when you want something prettier you need to restrain
> the horizontal width to get a consistent look across different screen
> resolutions. Almost every site (with fixed width) restrains the width to
> less than 800 pixels so that users with an 800x600 resolution don't need
> to scroll horizontally.

Sorry to disagree, but, fixed width and direct font size controlling,
isn't the good way to have a website looks good everywhere.

800x600 was the old "standard" resolution for PC under windows, and
windows desktop was thing for that size. But this isn't the cas
anymore, so what is the good size ? The answer won't be correct for
more than few years as it depends on price and most sold size of
monitor ...

So, using fixed width is bad, that's all. The only good way to made
web design is to add to your constraint the fact that the client will
never be the same, will never act the same way and every users may
have his own habits and taste. The best you can do is to make your
design with relative size against fixe size, font familly and not font
name and try to have something that can resist resizing (maybe under
some reasonable limits) whithout introducing unused space or
horizontal scrolling.

As I say earlier, using side bars (left, right or both) may solve some
problems. I agree to the fact the old site was a little bit heavy to
read the first time (I think I've never take the time to fully read
the first page ...) but there's a possible way for a "mix" of concept
...

Another point, is the fact that the outline generated by
validator.w3.org doesn't look good, it a sign of missuse of  tags
or bad page's organisation (normaly, this will give a good idea of the
page organisation, and should look like a table of contents, if it's
not the case, then something is wrong ... )

> To me, the new site looks nicer than the old one, and I'm pretty sure
> most people (specially and more importantly new visitors) will find it
> more attractive than the old one!

At some point, I'd say yes, in fact after the natural surprise of
finding a web site you know have changed, I found it no so bad, but a
better look at it shows some week point (size, and lack of usefull
contents, or much more appropriate the fact that some unimportant
informations is far better visible than it realy needs, and some other
informations, like actual release, are "shadowed".)

This make me think that it was just a proposal for a new website
design, but not the new production site, until I realize I was on the
www.freebsd.org page !

-- 
Burelle Marwan,
Equipe Bases de Donnees - LRI
http://www.cduce.org
([EMAIL PROTECTED] | [EMAIL PROTECTED])

pgpHJuKAUtuyJ.pgp
Description: PGP signature

Re: new FreeBSD-webpage

[Dave Fazio]

Totally agree and understand your point -- a graphical install option 
would mainly appeal to desktop users.  But let's be honest; considering 
the competition install base of  Red Hat, Mac OS X, SUN, and (ech!) 
Windows, the day of GUI deskop'd servers is here now; Purests hate it 
sure, but it's a fact, and shouldn't be discounted altogether as an 
option for modern day server configurations.


There's no point to digress more on this subject now, but FreeBSD is in 
my opinion the best of *all* general purpose OSs -- But to properly 
manage a FreeBSD (ports/packages,source builds, etc), the devil is 
definitely in the details.  Apple has smoothed our these details in 
short order -- why can't we? 


Regards,

-Dave


Marian Hettwer wrote:


Hej Dave,

Dave Fazio wrote:


In my opinion, this page will help popularize FreeBSD more than the
older (adding graphical installer would help too -- hint hint).

a graphical installer may help desktop users, but is totally unusable 
for server installations where you either want to install 
automatically (boot via pxe, mount some stuff via NFS, install the 
system, reboot and off you go) or where you just have serial access.


Anyway, the topic of graphical installer was discussed several times 
already :)


best regards,
Marian

PS.: I do like the layout of the new website :)




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

Re: new FreeBSD-webpage

[Greg Black]

On 2005-10-07, Murray Stokely wrote:
> On Fri, Oct 07, 2005 at 03:12:04PM +1000, Greg Black wrote:
>> To list the most critical issues:
>> 
>>   * Many important navigation links (e.g., the Handbook, the
>> Ports) disappeared from the front page.
> 
> The Handbook was added back to the front page hours ago in response to
> earlier posts.  If you cared about following such things, paying
> attention to CVS, or submitting patches you would have noticed.

It's there now.  It was not there when I wrote that -- I took
the time to check before I sent my message.  If you cared about
paying attention to things, you would have noticed.

> I've
> also proposed adding the Ports link to the shortcuts bar on the front
> page.  I agree with you here -- those are two very important links.

Splendid.
 
>>   * The user interface design is dreadful (e.g., fixed sizes for
>> things that cause all kinds of breakage when windows are
>> resized or font sizes changed to suit the reader).
> 
> Most feedback we have received would disagree with that statement.

Being part of the inner mafia, you may have access to more
information than I have.  But I've been reading several lists
and also participating in discussions in places you have no
access to and I can tell you that, although there are plenty of
people who like the new site, there are many who don't.  So I'm
going to go out on a limb and say you pulled that "most" out of
your arse.

And the ones who like it tend to be people who happen to have
default browser and window settings that happen to match
whatever the designers used.  Making a website -- especially a
technical site where information is much more important than
glitz -- dependent on specific sizes of elements is plain bad
design.

> Please provide patches for the CSS if the fixed width stuff bothers
> you so we can evaluate what you propose as being better.  It will be
> evaluated 100% fairly.  Show us your patches or be quiet on this
> point.

Ah, I see you're wearing your FreeBSD Advocacy hat.  No doubt
you think that a charming invitation like that will have the
audience jumping out of their skins to become a part of the
project so they too can be made to feel good by the friendly
team leaders.  If your designer can't fix the size stuff in 5
minutes without patches from me, then you need a new designer.

Let me put it in words of one syllable for you: don't try to
control font sizes (or styles); don't use fixed sizes for any
elements at all; relative sizes and percentages are all that is
needed.

>>   * Really boring junk has replaced real content on the front
>> page (e.g., lengthy list of new committers under the heading
>> of "news").
> 
> That content was already on the front page of the old site.

If what I said was really too hard to understand, try it this
way.  The old site had a lot of information that was really
useful visible or directly linked on the front page (and in the
first screenful as well).  The new site seems to treat lists of
new committers as something that deserves prominence on the
front page -- but the only people who care about that are the
new committers' mothers.

> The
> content of the news bar has not changed at all.  I have complained
> about the fact that we don't submit enough news stories for 4+ years.
> I fix it by adding lots of news items whenever I can think of
> one.

Good on you.

> Do
> you submit patches or PRs to submit more interesting news items?

Er, I wasn't complaining about lack of news items.  I was quite
specific: I wanted to see the ports and the handbook back on the
front. 

> If
> not, why complain when you are part of the problem?

I am part of the problem?  Get a grip.  You are a representative
of the project and you seem to think that gives you the right to
be insulting to people who have been FreeBSD advocates for many
years.  I have news for you: you have no such right.

>> Anyway, rather than protesting that the new thing is wonderful
>> and continually demanding "constructive" criticism from people
>> who are offering just that, why not listen to the suggestions
>> and see how to improve things?
> 
> Your mail has one constructive comment in it (About ports and handbook
> links belonging on the front page).  Everything else is a vague rant.

No, I had plenty of specific content.  You have an opinion that
differs from mine, so you call your opinion a fact.  But the
truth is just that we have different opinions.  You're entitled
to yours.  I'm entitled to mine.  But I made explicit points,
not just a vague rant.

> You vaguely say you don't like the design but don't offer any better
> alternative.

I said the fixed sizes and font control was a mistake.  How hard
is that for you to understand?

> That is not an impressive signal to noise ratio.
> Provide patches to your CSS / font complaints.

I covered this above.

>> site.  The claims that the old site was too hard to use that
>> have been advanced as the main reason for the update 

Switching from RELENG_4 to newer Release that supports ia64

[Michael Schuh]

Hello,

we plan to change the Hardware from one of our Servers Running RELENG_4.
The New Hardware becomes CPU-Types Xeon w/ EM64 -> ia64 architecture.

Now i have no experiences to change the OS-Release under the ass
from running Software (postfix/cyrus/postgresql/mysql/perletc.)

I be also not sure what release-version should i take.

My preferred opinion was to change to the upcoming RELENG_6,
but i be not sure if this is really a good idea, second i have no
documents found to migrate from RELENG_4 to RELENG_6.

I know it gives a very good description of changing the underlying
OS-Version to RELENG_5.

Another possible change is the Change to DragonFlyBSD.
But here is the same again, to less knowledge about this step.

Can anyone point's me to an good description for this switching,
or have anyone good experiences with the combinations of OS-Versions
resp. OS-Types (in case of DragonFlyBSD) with running Software
in production?

Iportant to know is also that this is an Hot-Production-Server.

Thanks for the suggestions.

best regards

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

Re: setsockopt and SO_RCV/SNDTIMEO

[Gleb Smirnoff]

  Lefteris,

On Fri, Oct 07, 2005 at 01:23:22AM +0300, Lefteris Tsintjelis wrote:
L> I am trying to set something like this up but it doesn't seem to work
L> as I expect it (unless I expect wrong):
L> 
L> timeout.tv_sec = 4;
L> timeout.tv_usec = 0;
L> if(setsockopt(listenSocket, SOL_SOCKET, SO_RCVTIMEO, (void *)&timeout, 
L> sizeof(timeout)) == -1)
L>  fprintf(stdout, "setsockopt SO_RCVTIMEO failed: %s\n", 
L>  strerror(errno));
L> if(setsockopt(listenSocket, SOL_SOCKET, SO_SNDTIMEO, (void *)&timeout, 
L> sizeof(timeout)) == -1)
L>  fprintf(stdout, "setsockopt SO_SNDTIMEO failed: %s\n", 
L>  strerror(errno));
L> 
L> When I telnet to the socket, the socket always stays connected. The
L> timer doesn't seem to work right. Am I missing anything here or is
L> this broken?

You are expecting wrong from these socket options. They do not specify
time after which socket should be closed, if no IO is done.

The do limit time the process can block on the socket. So, if you
do read() from this socket and it blocks, it will resume after 4 seconds
even if no input is present.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new FreeBSD-webpage

[Yann Golanski]

Can opened.. Worms everywhere.

-- 
[EMAIL PROTECTED]  -=*=-  www.kierun.org
PGP:   009D 7287 C4A7 FD4F 1680  06E4 F751 7006 9DE2 6318


pgpDNYdLHz61S.pgp
Description: PGP signature

Re: new FreeBSD-webpage

[Miguel Saturnino]

Hi!

On Thu, 2005-10-06 at 20:22 +0300, Tuomo Latto wrote:
> You'd expect popups from the links on the top (they look like that
> sort of links), but none seem to appear and I've just wasted time
> waiting for them to appear.

Why would you expect pop-up windows from the new menu? Why does this
menu looks like a menu that will pop up a new window? To me, it just
looks like a nice menu -- and I certainly don't expect pop-up windows
from it.

> With Opera, about 40% of the screen space is left unused.
> I *liked* the quick links the old one had on the sides.

If you try it with a screen resolution of 800x600 it will fill all the
screen ;) A fluid design can be more usable in different screen
resolutions, but when you want something prettier you need to restrain
the horizontal width to get a consistent look across different screen
resolutions. Almost every site (with fixed width) restrains the width to
less than 800 pixels so that users with an 800x600 resolution don't need
to scroll horizontally.


To me, the new site looks nicer than the old one, and I'm pretty sure
most people (specially and more importantly new visitors) will find it
more attractive than the old one!

Regards,

-- 
Miguel Saturnino

http://www.teiadigital.pt/  http://www.pelosanimais.org/
http://www.encontra-me.org/ http://www.esteriliza-me.org/

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

Re: new FreeBSD-webpage

[Peter Jeremy]

On Thu, 2005-Oct-06 20:22:06 +0300, Tuomo Latto wrote:
>Lynx Version 2.8.5rel.1 (04 Feb 2004) doesn't seem to handle XML,
>so when you're in a pinch with your fw/gw machine that doesn't have
>X installed and you quickly need to access eg. some documentation
>on the site, you're out of luck.

The first three links at the top of the new home page are in XML - they
appear to be the RSS news feeds.  The bits of documentation that I've
looked at are all in HTML.

It might be nicer if the RSS links were more clearly identified as
such but claiming that the website is incompatible with lynx is a bit
of an exaggeration.

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

[releng_6 tinderbox] failure on i386/pc98

[FreeBSD Tinderbox]

TB --- 2005-10-07 07:16:44 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-10-07 07:16:44 - starting RELENG_6 tinderbox run for i386/pc98
TB --- 2005-10-07 07:16:44 - cleaning the object tree
TB --- 2005-10-07 07:17:32 - checking out the source tree
TB --- 2005-10-07 07:17:32 - cd /tinderbox/RELENG_6/i386/pc98
TB --- 2005-10-07 07:17:32 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd 
-rRELENG_6 src
TB --- 2005-10-07 07:31:39 - building world (CFLAGS=-O -pipe)
TB --- 2005-10-07 07:31:39 - cd /src
TB --- 2005-10-07 07:31:39 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
TB --- 2005-10-07 08:22:56 - building generic kernel (COPTFLAGS=-O -pipe)
TB --- 2005-10-07 08:22:56 - cd /src
TB --- 2005-10-07 08:22:56 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Fri Oct  7 08:22:56 UTC 2005
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
>>> Kernel build for GENERIC completed on Fri Oct  7 08:34:10 UTC 2005
TB --- 2005-10-07 08:34:10 - generating LINT kernel config
TB --- 2005-10-07 08:34:10 - cd /src/sys/pc98/conf
TB --- 2005-10-07 08:34:10 - /usr/bin/make -B LINT
TB --- 2005-10-07 08:34:10 - building LINT kernel (COPTFLAGS=-O -pipe)
TB --- 2005-10-07 08:34:10 - cd /src
TB --- 2005-10-07 08:34:10 - /usr/bin/make buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Fri Oct  7 08:34:11 UTC 2005
>>> stage 1: configuring the kernel
--
cd /src/sys/pc98/conf;  
PATH=/obj/pc98/src/tmp/legacy/usr/sbin:/obj/pc98/src/tmp/legacy/usr/bin:/obj/pc98/src/tmp/legacy/usr/games:/obj/pc98/src/tmp/usr/sbin:/obj/pc98/src/tmp/usr/bin:/obj/pc98/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /obj/pc98/src/sys/LINT  /src/sys/pc98/conf/LINT
config: Error: device "pcic" is unknown
config: Error: device "card" is unknown
config: 2 errors
WARNING: kernel contains GPL contaminated ext2fs filesystem
WARNING: kernel contains GPL contaminated ReiserFS filesystem
WARNING: COMPAT_SVR4 is broken and should be avoided
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2005-10-07 08:34:11 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2005-10-07 08:34:11 - ERROR: failed to build lint kernel
TB --- 2005-10-07 08:34:11 - tinderbox aborted

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

Re: new FreeBSD-webpage

[Marian Hettwer]

Hej Dave,

Dave Fazio wrote:

In my opinion, this page will help popularize FreeBSD more than the
older (adding graphical installer would help too -- hint hint).

a graphical installer may help desktop users, but is totally unusable 
for server installations where you either want to install automatically 
(boot via pxe, mount some stuff via NFS, install the system, reboot and 
off you go) or where you just have serial access.


Anyway, the topic of graphical installer was discussed several times 
already :)


best regards,
Marian

PS.: I do like the layout of the new website :)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new FreeBSD-webpage

[Murray Stokely]

On Fri, Oct 07, 2005 at 03:12:04PM +1000, Greg Black wrote:
> To list the most critical issues:
> 
>   * Many important navigation links (e.g., the Handbook, the
> Ports) disappeared from the front page.

The Handbook was added back to the front page hours ago in response to
earlier posts.  If you cared about following such things, paying
attention to CVS, or submitting patches you would have noticed.  I've
also proposed adding the Ports link to the shortcuts bar on the front
page.  I agree with you here -- those are two very important links.

>   * The user interface design is dreadful (e.g., fixed sizes for
> things that cause all kinds of breakage when windows are
> resized or font sizes changed to suit the reader).

Most feedback we have received would disagree with that statement.
Please provide patches for the CSS if the fixed width stuff bothers
you so we can evaluate what you propose as being better.  It will be
evaluated 100% fairly.  Show us your patches or be quiet on this
point.

>   * Really boring junk has replaced real content on the front
> page (e.g., lengthy list of new committers under the heading
> of "news").

That content was already on the front page of the old site.  The
content of the news bar has not changed at all.  I have complained
about the fact that we don't submit enough news stories for 4+ years.
I fix it by adding lots of news items whenever I can think of one.  Do
you submit patches or PRs to submit more interesting news items?  If
not, why complain when you are part of the problem?

> Anyway, rather than protesting that the new thing is wonderful
> and continually demanding "constructive" criticism from people
> who are offering just that, why not listen to the suggestions
> and see how to improve things?

Your mail has one constructive comment in it (About ports and handbook
links belonging on the front page).  Everything else is a vague rant.
You vaguely say you don't like the design but don't offer any better
alternative.  That is not an impressive signal to noise ratio.
Provide patches to your CSS / font complaints.

> site.  The claims that the old site was too hard to use that
> have been advanced as the main reason for the update just don't
> hold water, as far as I'm concerned.

You're welcome to hold that opinion.  I don't care to debate you on
it.  It's just not fair when you act like we are not concerned with
valid criticism when it comes our way.  Changes to valid points have
been made within hours of them first being brought up on the lists.
We've made even more changes to the design in response to feedback
over the past few months.

> Anyway, I see that the people in charge will do whatever they
> want and it will be up to the rest of us to make the best of it.

The people in charge worked very hard over 6 months to get broad
consensus for this change.  If you were interested in being a part of
this process you should have been subscribed to freebsd-www@, read the
front page where we announced a summer of code student was working a
redesign, read through the developer status reports, watched the CVS
logs, or any of the other many different methods you could have stayed
informed about the new design work.

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