from:"Allen"

Another data point:

I did the whole experiment with the latest 12-STABLE but for amd64 and 
everything builds fine without changes, and runs fine too.

I used the same src.conf and make.conf.  So the problem is definitely with i386.

Dan

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

re: ifuncs check flawed?

Well, everything built fine, but the kernel faults on boot, so the checks are 
probably needed. ;-)

I still do not understand why the linker that is part of 12-STABLE does not 
provide the support needed.

The directives in my src.conf and make.conf do not delete the lld linker.  They 
just cut down on extra llvm parts that I do not need, or so I am led to believe.

Still puzzled.

Dan


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

re: ifuncs check flawed?

The ifuncs check for buildkernel is identical to the one in 

  /usr/src/lib/libc/Makefile

and is here:

  /usr/src/sys/conf/kern.pre.mk

Dan

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

ifuncs check flawed?

I have been building FreeBSD for many years, as in since 2.2.8.

Currently my amd64 build of 12-STABLE is built with the following src.conf:

WITHOUT_BHYVE=1
WITHOUT_CAPSICUM=1
WITHOUT_CDDL=1
WITHOUT_CLANG_EXTRAS=1
WITHOUT_CLANG_FULL=1
WITHOUT_CROSS_COMPILER=1
WITHOUT_DEBUG_FILES=1
WITHOUT_EXAMPLES=1
WITHOUT_HYPERV=1
WITHOUT_JAIL=1
WITHOUT_LOCALES=1
WITHOUT_PROFILE=1
WITHOUT_QUOTAS=1
WITHOUT_TESTS=1

And a make.conf of:

BATCH=yes
MK_CDDL=no
MK_CLANG_EXTRAS=no
MK_DEBUG_FILES=no
MK_NO_PROFILE=yes
MK_TESTS=no
OPTIONS_UNSET=JAVA
WITH_JADETEX=no
WITHOUT_CDDL=yes
WITHOUT_CLANG_FULL=yes
WITHOUT_CTF=yes
WITHOUT_CTM=yes
DISABLE_VULNERABILITIES=yes

So far, so good.  (I do this to fit the whole thing onto a CD-image.)

Fooling around, and using xhyve on my Mac, I want to build a i386 version in a 
VM.

So I grabbed the 20190314 snapshot of 12-STABLE, i386 flavor, and installed it. 
 Works great.

Now to rebuild the world.

The buildworld and buildkernel steps both immediately fail due to the linker 
not supporting ifuncs.

The code that stops the buildworld is this from /usr/src/lib/libc/Makefile:

---
.if (${LIBC_ARCH} == amd64 || ${LIBC_ARCH} == i386) && \
 ${.TARGETS:Mall} == all && \
 defined(LINKER_FEATURES) && ${LINKER_FEATURES:Mifunc} == ""
.error ${LIBC_ARCH} libc requires linker ifunc support
.endif
---

However the linker on my system is the lld linker that supports ifuncs!  Why 
does this check fail?

I am building on i386 but I am only building i386, as in I am not building all 
targets or amd64.

I edited the two Makefiles that have this check to remove the check and the 
builds proceed just fine.

So it appears that these checks are flawed, or I am soon to learn something new 
about FreeBSD!

Thanks,

Dan Allen



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: aesni on i386 w/gcc breaks 11-STABLE kernel build

2018-05-31 Thread Dan Allen

> On 30 May 2018, at 12:13 PM, Dimitry Andric  wrote:
> 
> Probably only the module should be disabled,

I did this my deleting a few lines from /usr/src/sys/modules/Makefile, and 
everything works well now!

A fully gcc-based 11-STABLE i386 machine.  (The builds go SO much faster with 
gcc rather than clang!)

So there are still two bugs:

1) I think there should be a check in /usr/src/sys/modules/Makefile for the 
lack of clang that disables building the aesni module.

2) Upon boot there is a progress line right at the start that still says clang 
6.0.0, even though clang does not exist on the machine.
This should print gcc on a system configured like mine.

Here is my src.conf:

WITH_GCC=1
WITH_GCC_BOOTSTRAP=1
WITHOUT_BHYVE=1
WITHOUT_CAPSICUM=1
WITHOUT_CDDL=1
WITHOUT_CLANG=1
WITHOUT_CLANG_BOOTSTRAP=1
WITHOUT_CLANG_EXTRAS=1
WITHOUT_CLANG_FULL=1
WITHOUT_CROSS_COMPILER=1
WITHOUT_DEBUG_FILES=1
WITHOUT_EXAMPLES=1
WITHOUT_HYPERV=1
WITHOUT_JAIL=1
WITHOUT_LOCALES=1
WITHOUT_PROFILE=1
WITHOUT_QUOTAS=1
WITHOUT_TESTS=1

Dan

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

aesni on i386 w/gcc breaks 11-STABLE kernel build

2018-05-29 Thread Dan Allen

To Whom It May Concern:

I am building FreeBSD 11 stable i386 on an old Pentium 4 machine.  The 
clang/llvm build is just horrific in length, so I am substituting gcc by the 
appropriate /etc/src.conf defines such as WITHOUT_CLANG, 
WITHOUT_CLANG_BOOTSTRAP, WITH_GCC, WITH_GCC_BOOTSTRAP.  

After deleting clang via make delete-old in /usr/src, all of userland builds 
fine, but the kernel will not build due to the aesni module.

The build break is due to compiling /usr/src/sys/crypto/aesni/aesni_ghash.c, 
which in turn #includes wmmintrin.h, emmintrin.h, and smmintrin.h which are all 
clang-specific headers.

I am rebuilding with MK_CRYPT=no to see if this works around the problem, but 
it seems like perhaps just this one aesni module should not be built rather 
than all of CRYPT having to be disabled.

This is a post 11.2 BETA3 sync to STABLE as of today, 29 May 2018.

Dan



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: amd64 kernel crash introduced between 20180329 & 20180408

2018-04-17 Thread Dan Allen

> On 17 Apr 2018, at 9:24 AM, Kyle Evans  wrote:
> 
> Can you set vm.pmap.pti=0 at the loader prompt and see if
> this affects your situation at all, just to rule that out?

I redid everything from the start, did set vm.pmap.pti=0, and it behaves 
exactly the same: kernel panic.

Thanks for your help!

Do I have any other takers?  ;-)

Dan

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: amd64 kernel crash introduced between 20180329 & 20180408

2018-04-17 Thread Dan Allen

> On 17 Apr 2018, at 8:49 AM, Kyle Evans  wrote:
> 
> As "the guy most likely to have broken boot code in stable," may I ask
> what leads you specifically to amd64 boot code? Mostly curious if
> there's something beyond "i386 works well" that lead you to this
> conclusion.

It is partly just a hunch.

I installed 11.0 for use with qemu a while ago.  I did binary upgrades for 
patches using
freebsd-update.  When 11.1 came out, it would not work correctly, again with 
the same
kind of behavior.  Then, I got some later snapshots that worked again, notably 
the 20180329
build.  When the next snapshot came out, things broke.  I also tried my own 
builds, same story.

I even got both source trees together - 20180329 and 20180408 - and did a diff 
on the entire
trees, and I noticed activity in the boot & kernel code.  It could just as 
likely be something in the
kernel as well, but none of this happens with the i386 build.

> When you say it crashes and does a kernel dump- you're landing at a
> ddb prompt, yeah? What does executing bt at that prompt look like?

No, I am not ever given a prompt.  I get to watch a mini-dump happen and then 
an automatic
reboot.  It is a kernel panic.  Here is what I see:

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

amd64 kernel crash introduced between 20180329 & 20180408

2018-04-17 Thread Dan Allen

I run FreeBSD 11-STABLE on actual machines, and I build the system every few
days. Things have been fine.

However, I also run FreeBSD 11 via the qemu emulator on my Mac. I run lots of
different BSD & Linux OSes here to test them out. I have been running the same
binary of qemu-system-x86_64 v1.2 for six years. It runs great.

Then recently this happened:

This snapshot dated 20180329, after doing a fresh install, runs fine:

https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180329-r331742-disc1.iso

I can run pkg install and begin adding stuff to the system and life is good.

BUT

This snapshot dated 20180408, after doing a fresh install, will crash when
running pkg install:

https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180408-r332308-disc1.iso

It crashes about 90% of the way through updating the pkg snapshot. It does not
matter what pkg you try and install.

However, the latest release in the i386 flavor works fine on qemu:

https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-i386-20180412-r332428-disc1.iso

So sometime between March 29th & April 8th, in amd64 boot code, I believe the
problem was introduced.

I cannot debug the crash, because it does a kernel dump, and then when the
system reboots, almost anything again triggers a kernel crash and it reboots
again and again: no chance to inspect a mini dump or whatever.

I wish I had more to go on, but I am happy to off list work with anyone that
wants to pursue this, by testing out stuff or answering more questions.

Dan Allen
Running FreeBSD since 2.2.8
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

/lib/libzfs_core.so.2 obsolete?

2015-07-09 Thread Dan Allen

I sync and build 10.1-stable almost daily.  I keep up with mergemaster as well 
as make delete-old-files, and even so, I found in my /lib directory that one 
library is from last Nov 2014 even though everything else is dated today (I 
built everything today).

So, my assumption is that /lib/libzfs_core.so.2 should be added to the 
ObsoleteFiles.inc file.

Dan Allen
Building FreeBSD since 2.2.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: local APIC error 0x40

2012-08-01 Thread Dan Allen


On 31 Jul 2012, at 2:39 PM, John Baldwin j...@freebsd.org wrote:

 On Tuesday, July 24, 2012 9:32:45 pm Dan Allen wrote:
 
  $FreeBSD: src/sys/i386/i386/machdep.c,v 1.688.2.31 2012/06/13 15:25:52 jhb 

 So to be clear, does that revision work fine, it's a future revision that 
 breaks things, or does that revision break?

The revision of 2012/06/13 works fine.  It is later versions that are broken.  
(It is also broken in BSD 9.0 and later.)

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: local APIC error 0x40

2012-08-01 Thread Dan Allen


On Aug 1, 2012, at 10:06 AM, John Baldwin j...@freebsd.org wrote:

 Can you use a binary search on the date to narrow down which commit breaks it?

Sadly, I cannot.  I upgraded the machine to RELENG_9.  The powerd demon appears 
to control the fan okay now.  However I still must use the apic hint in 
loader.conf to turn off my 2nd core or else I get flooded with that 0x40 
error message.

Today running in 9.1 PRERELEASE I have a quiet fan, only one core, and I have 
got a stray irc7 message a couple of times.  This is all on my Core Duo 
Toshiba Satellite U205.

Meanwhile, on a Pentium 4 and a tiny Dell Mini 10 Inspiron with an Intel Atom 
chip, everything is fine with RELENG_9.  It is just this Toshiba, which ran 
perfectly for years with FreeBSD 6, 7, but things have declined with 8.0 and 
later.

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: local APIC error 0x40

2012-07-24 Thread Dan Allen


On 24 Jul 2012, at 4:26 AM, Konstantin Belousov kostik...@gmail.com wrote:

 Does your system slows down with these messages ? 0x40 means that some
 code tried to send IPI with interrupt number from the range of assigned
 CPU faults. I believe that FreeBSD code never does that.
 
 Is there a BIOS upgrade for your machine ?

No, the system does not slow down.  I am checking on the BIOS upgrade.

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: local APIC error 0x40

2012-07-24 Thread Dan Allen


On 24 Jul 2012, at 4:26 AM, Konstantin Belousov kostik...@gmail.com wrote:

 Does your system slows down with these messages ? 0x40 means that some
 code tried to send IPI with interrupt number from the range of assigned
 CPU faults. I believe that FreeBSD code never does that.

So, I reverted to 

  $FreeBSD: src/sys/i386/i386/machdep.c,v 1.688.2.31 2012/06/13 15:25:52 jhb 
Exp $

and rebuilt the kernel.  By making that one change my fan problem is fixed!  No 
more 0x40 msgs, although I only have 1 core again due to my use of 
hint.apic.0.disabled=1 in /boot/loader.conf.

So, the most recent changes done to machdep.c are the culprit!

I also booted from a FreeBSD 9.0 CD and it has the same string of 0x40 error 
messages with its default configuration and an empty /boot/loader.conf file, so 
both the latest changes to BSD 8.3 as well as the BSD 9.0+ tree have got 
dealing with Intel Core Duo chips wrong.  (My Pentium 4 and Intel Atom machines 
running RELENG_9 are fine and show no problems.  It is just my old Toshiba 
Satellite U205 w/Core Duo that has these problems.)

I booted from an OpenBSD 5.0 CD and it works just fine in every way.  Maybe 
I'll just run OpenBSD 5 on the Toshiba and call it a day.

Dan



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

local APIC error 0x40

2012-07-23 Thread Dan Allen

Running FreeBSD 8.3 -- and updating sources on a daily base and building 
everything -- I found a new APIC/ACPI problem introduced in the past week.

I have a Toshiba Satellite U205 with an Intel Core Duo (not a Core 2).  It used 
to work fine with both cores but then sometime in on the road to BSD 8.0 the 
machine began hanging.  So I added to /boot/loader.conf

  hint.apic.0.disabled=1

and the machine only had one core but it went back to being reliable.

The laptop sits idle a lot, so I also have in /etc/rc.conf

  performance_cx_lowest=LOW

and the fans stay off unless I am doing a build.  Everything was good.

I went away on a trip last week for five days, came home, did a csup to 
RELENG_8 and rebuilt the world, as usual, and now the fans are always running 
full!

If I comment out hint.apic.0.disabled=1 from /boot/loader.conf and reboot, 
the results are a mixed bag:

1) I get my 2nd core back, and it no longer hangs! Hurray.
2) The fans go back to usually being off and silent.  Hurray!
3) I get zillions of error messages streaming saying:

  CPU0: local APIC error 0x40
  CPU1: local APIC error 0x40

No good!


I am sitting at a prompt, no X-Windows, no apps running (other than the usual 
demons), and every few seconds I get another pair of these error messages.

4) The error appears benign other than flooding the console.  Everything works, 
nothing hangs, I can build the OS and everything appears fine.

So how do I get rid of these messages?  What does error 0x40 mean?

Thanks,

Dan Allen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

ACPI broke going from 8 to 9

(** Originally posted to freebsd-curr...@freebsd.org but I noticed that there 
are 9.0 RC3 questions here on freebsd-stable; I am not sure which forum is 
appropriate. **)

I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9.  The machine 
no longer boots.  However, if I put

 hint.acpi.0.disabled=1

in /boot/loader.conf then the machine runs fine.  With RELENG_8 the machine had 
no loader.conf, and the power button worked on my desktop machine.  Now with 
ACPI disabled my power button does not work.  I have found that the machine 
hangs at boot during a scan of the PCI bus, but if I disable that 
(hw.acpi.disable=pci) then the machine cannot find a boot drive.

So I have lost functionality that worked fine in BSD 8.

Thoughts?  Suggestions?

Thanks,

Dan Allen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ACPI broke going from 8 to 9


On 31 Dec 2011, at 10:57 AM, Jeremy Chadwick wrote:

 Do you have a necessary reason to upgrade to 9 given this situation?
 Given the conditions I would stay you should stay with 8.

This philosophy seems wrong, but it may be the way to go.

My Toshiba Satellite U205 used to work great with RELENG_7, but the boot code 
of RELENG_8 will not recognize the 2nd core of my Core Duo (not Core 2 Duo) 
processor.  Nobody seems to care as few machines have Core Duo, or few people 
use this era of Toshiba BIOS, or whatever.

Now my Dell GX270 ACPI code is pre 2.0 (so Garrett tells me), so RELENG_9 is 
out.

I guess I should run all of my older machines on RELENG_7 but -- and this is 
where the philosophy you suggest seems wrong -- I still want the latest apps, 
security fixes, etc.  If the stable tree updates ls or tcsh or awk, I want 
these, but the core OS seems to have moved on from 2004 machines.

In other words, there is no tree for me.

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ACPI broke going from 8 to 9


On 31 Dec 2011, at 1:01 PM, Adrian Chadd wrote:

 So what I can only suggest is that you build and boot a variety of
 -HEAD kernels. Start with HEAD from say, Jan 1 2011. Boot it, see if
 it works. If it doesn't, go back 3 months at a time. If it does, go
 forward three months until it breaks.

Fair enough.  I will see what I can accomplish.  Thanks!

Dan


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ACPI broke going from 8 to 9


On 31 Dec 2011, at 12:34 PM, Garrett Cooper wrote:

 Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and
 try booting the new kernel. See if this works.

It worked!  No hang, power button works.  Nice.  I hope this experimental 
option stays in.

Thank you everyone for your help.  Happy New Years!

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ACPI broke going from 8 to 9


On 31 Dec 2011, at 4:31 PM, Jeremy Chadwick wrote:

 In the meantime: Dan, when you say in your original mail, I just
 upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9, can you
 please provide uname -a output from the system when it was running
 RELENG_8?  I'm looking specifically for the exact time when the kernel
 was built

Almost every day I csup from RELENG_x and build.  The traces of RELENG_8 are 
gone, so no, unfortunately I cannot give you a uname -a from those days.

However, I have a build log file, and I see that I moved from RELENG_8 to 
RELENG_9 on Friday, Dec 23, 2011.  I csup'd at 12:24:26 MST and discovered the 
failure at 15:41 MST.

This nooptions NEW_PCIB fix does seem rather tenuous if it is not documented. 
 Wouldn't a better route be something like

  if (ACPI  2.0)
oldCode();
  else
newCodeForNewACPI();

so that it will always work for everyone without having to build a special 
kernel?  After all, I went from a working system to a hung system which is not 
the best upgrade path... ;-)

Dan



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Build Broken: /usr/src/usr.bin/netstat/inet.c

2011-01-04 Thread Dan Allen

I just did a csup of stable, and the build is broken.

In function protopr various struct members are not defined.  The build halts.

First compile error is at /usr/src/usr.bin/netstat/inet.c line 462

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ntpd fails on boot

2010-12-18 Thread Dan Allen


On 14 Dec 2010, at 5:47 PM, Jeremy Chadwick wrote:

 Anyway, many people are using the below with success.

Sorry to say that netwait did NOT in the end fix the problem.

I however discovered that if I put

  synchronous_dhclient=YES

into my /etc/rc.conf file, that over many days  reboots now has
been delivering reliable networking such that ntpd always works.

Thanks again to everyone for their help.

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ntpd fails on boot

2010-12-15 Thread Dan Allen


On 14 Dec 2010, at 7:02 PM, Jeremy Chadwick wrote:

 The design model of these daemons is to assume network connectivity is 
 working when they start, and netwait
 reliably ensures that.

Thanks Jeremy for the script.  It works like a charm on my system, fixing the 
problem.

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

ntpd fails on boot

2010-12-14 Thread Dan Allen

Recently my network connection now is setup AFTER ntpd is launched rather than 
before.

So when ntpd starts there is no net connection and it gives up.

I read /usr/src/UPDATING but nothing is mentioned about a change in boot order.

Any ideas?

Thanks,

Dan Allen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: ntpd fails on boot

2010-12-14 Thread Dan Allen


On 14 Dec 2010, at 5:47 PM, Jeremy Chadwick wrote:

 This issue has been discussed pretty thoroughly in the past.  There's no
 official solution, but there is an rc.d script I wrote which addresses
 this shortcoming.  Nothing related to the boot order has changed, but
 network drivers and overall methodology has changed.

Thanks: I will give your script a try.

FYI: it has worked fine for about 15 years of my using FreeBSD until recently!

The other solution would be for ntpd to not just give up the first time it 
looks for the net.  It could try again a minute later and it would work just 
fine.  Apparently it never tries a second time!

This is something that should just work out of the box, IMHO.

Thanks everyone for your help!

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 8 Nov 2010, at 10:30 PM, Andriy Gapon wrote:

 Can you please also provide the following output:
 $ kenv | fgrep hint.acpi

hint.acpi.0.oem=TOSHIB
hint.acpi.0.revision=1
hint.acpi.0.rsdp=0xf01e0
hint.acpi.0.rsdt=0x3f7a

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 9 Nov 2010, at 8:11 AM, Andriy Gapon wrote:

 - sysctl machdep.acpi_root

machdep.acpi_root: 983520

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 9 Nov 2010, at 8:11 AM, Andriy Gapon wrote:

 /boot/loader.conf contents

This might be the smoking gun!

cat loader.conf:

hint.apic.0.disabled=1

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 9 Nov 2010, at 8:24 AM, Andriy Gapon wrote:

 on 09/11/2010 17:22 Dan Allen said the following:
 
 On 9 Nov 2010, at 8:11 AM, Andriy Gapon wrote:
 
 /boot/loader.conf contents
 
 This might be the smoking gun!
 
 cat loader.conf:
 
  hint.apic.0.disabled=1
 
 Yes, it is.
 So why do you have it and what happens if you remove it?

Well, there is good news and bad news.

The good news is that if I remove this hint the machine boots with 2 CPUs.

The bad news is that I get lots of:

  CPU0: local APIC error 0x40
  CPU1: local APIC error 0x40

messages and the machine is very unresponsive.  Every keystroke has a second or 
two of delay.  It really is unusable.

If memory serves I had to turn off APIC in order to see both CPUs at some time 
in the past.  However, at some time in the past I had both CPUs and did not 
have the severe unresponsiveness that I get without this hint.

So with APIC I get both CPUs but an unusable config.  Without APIC I have one 
CPU but things are lively.

What next?

Dan


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 9 Nov 2010, at 9:07 AM, Andriy Gapon wrote:

 Let's see if anybody else can help you with that stuff.
 My jurisdiction (area of expertise) ends here.

Thank you for your help!

Dan


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 9 Nov 2010, at 3:08 PM, Andriy Gapon wrote:

 The kernel should still not panic if someone disables APIC.
 
 100% agreement - and it shouldn't do that now.

The kernel on my Core Duo machine does not panic with APIC off.  In fact it 
works much better with it off.  The only problem is that I am missing one of my 
two Cores with APIC off!

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18

2010-11-08 Thread Dan Allen


On 5 Nov 2010, at 9:22 AM, Andriy Gapon wrote:

 Let's look at the following:
 0. your kernel config
 1. verbose dmesg
 2. acpidump -dt output
 3. x86info -a (sysutils/x86info)

Andriy, I sync'd with CURRENT and got your patch today as part of the official 
sources.  My machine at least boots up fine, but still with just one logical 
CPU...

Attached is a zip file containing all of the 4 outputs as requested above.

Dan




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18

2010-11-05 Thread Dan Allen


On 3 Nov 2010, at 2:40 AM, Andriy Gapon wrote:

 This problem seems to happen only on SMP systems that for some reason run as 
 UP.
 E.g. because ACPI and/or APIC are disabled.
 Or some other BIOS configuration.
 But I am not sure what exactly is the case here.

Okay, I have been researching my UP/SMP problem.

In the past, before recent Intel topology changes, on my Toshiba Satellite 
U205 machine if I used a kernel with ACPI support, only 1 logical CPU showed up 
in FreeBSD 8.1-STABLE.  When I booted into Windows XP on the same machine, with 
the same BIOS settings, I would see 2 logical CPUs.  If I built a FreeBSD 
kernel WITHOUT ACPI support and left the BIOS settings as they were above, I 
then would see 2 logical CPUs.

Now with these recent FreeBSD changes I cannot get the machine to EVER 
recognize a 2nd logical processor, but if I boot into Windows XP I still see 
two CPUs, so we still have a bug in this new Intel topology code.

This laptop has an Intel Core Duo T2400 @ 1.83 GHz chip.  (The BIOS is set to 
provide multiple logical CPUs in all cases and Andriy, I am using your patched 
kernel.)

Is there anything else I can do to help you understand this system config?

What next?

Dan



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 3 Nov 2010, at 2:48 AM, Andriy Gapon wrote:

 I still would like to see verbose dmesg, just to be sure what's going on.

Here is the output of dmesg from the last working kerneL, with sources sync'd 
Oct 28th:

Dan

---

Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.1-STABLE #2: Thu Oct 28 14:56:36 MDT 2010
r...@u205.airwired.net:/usr/obj/usr/src/sys/DKA i386
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Genuine Intel(R) CPU   T2400  @ 1.83GHz (1828.76-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x6e8  Family = 6  Model = e  Stepping = 8
  
Features=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Features2=0xc1a9SSE3,MON,VMX,EST,TM2,xTPR,PDCM
  TSC: P-state invariant
real memory  = 1073741824 (1024 MB)
avail memory = 1027780608 (980 MB)
WARNING: Non-uniform processors.
WARNING: Using suboptimal topology.
kbd1 at kbdmux0
acpi0: TOSHIB 750 on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, 3f6a (3) failed
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0xd808-0xd80b on acpi0
cpu0: ACPI CPU on acpi0
acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
Timecounter HPET frequency 14318180 Hz quality 900
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
vgapci0: VGA-compatible display port 0xcff8-0xcfff mem 
0xffd8-0xffdf,0xe000-0xefff,0xffd4-0xffd7 irq 10 at 
device 2.0 on pci0
agp0: Intel 82945GM (945GM GMCH) SVGA controller on vgapci0
agp0: detected 7932k stolen memory
agp0: aperture size is 256M
vgapci1: VGA-compatible display mem 0xffc8-0xffcf at device 2.1 on 
pci0
pci0: multimedia, HDA at device 27.0 (no driver attached)
pcib1: ACPI PCI-PCI bridge irq 11 at device 28.0 on pci0
pci1: ACPI PCI bus on pcib1
pcib2: ACPI PCI-PCI bridge irq 11 at device 28.2 on pci0
pci2: ACPI PCI bus on pcib2
pci2: network at device 0.0 (no driver attached)
uhci0: Intel 82801G (ICH7) USB controller USB-A port 0xcf80-0xcf9f irq 11 at 
device 29.0 on pci0
uhci0: [ITHREAD]
usbus0: Intel 82801G (ICH7) USB controller USB-A on uhci0
uhci1: Intel 82801G (ICH7) USB controller USB-B port 0xcf60-0xcf7f irq 11 at 
device 29.1 on pci0
uhci1: [ITHREAD]
usbus1: Intel 82801G (ICH7) USB controller USB-B on uhci1
uhci2: Intel 82801G (ICH7) USB controller USB-C port 0xcf40-0xcf5f irq 11 at 
device 29.2 on pci0
uhci2: [ITHREAD]
usbus2: Intel 82801G (ICH7) USB controller USB-C on uhci2
uhci3: Intel 82801G (ICH7) USB controller USB-D port 0xcf20-0xcf3f irq 10 at 
device 29.3 on pci0
uhci3: [ITHREAD]
usbus3: Intel 82801G (ICH7) USB controller USB-D on uhci3
ehci0: Intel 82801GB/R (ICH7) USB 2.0 controller mem 0xffd3bc00-0xffd3bfff 
irq 11 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus4: EHCI version 1.0
usbus4: Intel 82801GB/R (ICH7) USB 2.0 controller on ehci0
pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0
pci3: ACPI PCI bus on pcib3
fxp0: Intel Pro/100 VE Network Connection port 0xbf40-0xbf7f mem 
0xff9ff000-0xff9f irq 11 at device 8.0 on pci3
miibus0: MII bus on fxp0
inphy0: i82562ET 10/100 media interface PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:0e:7b:30:ca:e5
fxp0: [ITHREAD]
cbb0: PCI-CardBus Bridge at device 11.0 on pci3
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
cbb0: [FILTER]
fwohci0: 1394 Open Host Controller Interface mem 
0xff9fe800-0xff9fefff,0xff9f8000-0xff9fbfff irq 11 at device 11.1 on pci3
fwohci0: [ITHREAD]
fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:00:39:00:00:96:6a:bb
fwohci0: Phy 1394a available S400, 3 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: IEEE1394(FireWire) bus on fwohci0
fwe0: Ethernet over FireWire on firewire0
if_fwe0: Fake Ethernet address: 02:00:39:96:6a:bb
fwe0: Ethernet address: 02:00:39:96:6a:bb
fwip0: IP over FireWire on firewire0
fwip0: Firewire address: 00:00:39:00:00:96:6a:bb @ 0xfffe, S400, maxrec 
2048
dcons_crom0: dcons configuration ROM on firewire0
dcons_crom0: bus_addr 0x1078000
fwohci0: Initiate bus reset
fwohci0: fwohci_intr_core: BUS reset
fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1, CYCLEMASTER mode
pci3: mass storage at device 11.2 (no driver attached)
pci3: base peripheral, SD host controller at device 11.3 (no driver attached)
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel ICH7M SATA150 controller port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xafa0-0xafaf irq 11 at device 31.2 on pci0
ata0: ATA channel 0 on atapci0
ata0: [ITHREAD]
ata1: ATA

Re: Fatal trap 18


On 3 Nov 2010, at 2:18 AM, Sergey Kandaurov wrote:

 +   if (cpu_logical == 0)
 +   cpu_logical = 1;/* XXX max_logical? */
cpu_cores /= cpu_logical;
hyperthreading_cpus = cpu_logical;

My machine contains an Intel Core Duo, not a Core 2 Duo.  However, both 
machines have 2 logical CPUs.  Perhaps the bug is not handling a Core Duo 
properly.

I just sync'd with csup's date command as Jeremy suggested.  It is building 
right now.  We'll see if a 2010.10.28.06.00.00 GMT system has the problem.  I 
doubt it does.  I think this Intel logical CPU code business is probably the 
culprit.

It is hard to believe that I am the only one with a Core Duo machine finding 
this problem!

More in a bit...

Dan


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 2 Nov 2010, at 11:57 PM, Jeremy Chadwick wrote:

 Can you please roll your source code back to a date prior to the above
 commit, rebuild, and re-try?  You can accomplish this using the date
 option in your cvsup/csup file.  See csup(1) for details.  I would
 recommend also chopping off an additional hour just in case.

I did this and the results are as expected, i.e., everything worked just fine.

So we are zeroing in on this...

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 3 Nov 2010, at 2:01 PM, Andriy Gapon wrote:

 P.S. so will you be trying the patch I proposed?

Yes.  I will csup with today's sources and then apply the patch.

Results soon...

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Fatal trap 18


On 3 Nov 2010, at 3:09 PM, Jeremy Chadwick wrote:

 Anyway, it sounds like me testing isn't necessary since you have a
 pretty good idea of what's going on with Dan's setup.

Well I am certainly testing, and the patch that Andriy posted WORKS!

Steps:

1.  I csup'd to today's very latest sources.
2.  Installed the patch.
3.  Rebuilt and reinstalled the kernel.
4.  Boots up fine!

So, will this patch be integrated into STABLE soon?

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Fatal trap 18

2010-11-02 Thread Dan Allen

FreeBSD 8.1-STABLE sometime after 10/28/2010 has caused a fatal boot error on 
my Toshiba U205, 1.8 GHz Core Duo laptop.

Many times every week I sync with STABLE and build everything.  I have been 
doing this for years.

I sync'd (via csup) and built on 10/28/2010 and everything was fine.

Then I sync'd yesterday 11/1/2010 and it crashes on boot.  The diagnostics 
print out the following:

---

Fatal trap 18: integer divide fault while in kernel mode

kdb_backtrace
panic
trap_fatal
trap
calltrap
topo_probe
cpu_topo
smp_topo
sched_setup
mi_startup

---

I reverted at the loader via boot /boot/kernel.old, resync'd today, rebuilt, 
and things are still broken.

Any ideas?

Dan Allen



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Going to BSD 8 from RELENG_7

2009-08-13 Thread Dan Allen

I cvsup and build RELENG_7 many times a week.  This has served me well  
(except for the ZFS boot problem I had that went in and was backed  
out) for quite a while.


I like to track a STABLE release.  When BSD 7 went to 7.1 and to 7.2,  
it all just happened automatically with the way I do things.


Now I am interested on one of my BSD machines to try 8.0.  I need to  
change my cvsup target from RELENG_7 to CURRENT I believe.  Is that  
true?  When will STABLE become 8.0?


Also, does anyone know if there is a project page that talks about  
8.0, its timeline, its features, etc?  If you type 8.0 into the main  
freebsd.org web page it find nothing on the entire web site.   
Obviously something is wrong...


Thanks!

Dan Allen
Spring Lake, Utah





___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Let's back out LOADER_ZFS_SUPPORT from STABLE

2009-06-14 Thread Dan Allen



On 14 Jun 2009, at 10:38 AM, CmdLnKid wrote:


Is it possible that you have most likely been playing around with ZFS
before this and left some of the configurations of ZFS embedded in  
your

drive and the loader is picking that up.


No, I have never used ZFS.

The drive is partitioned and the first partition has Windows XP Pro on  
it, so I assume that this may be the problem.


Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Let's back out LOADER_ZFS_SUPPORT from STABLE

2009-06-14 Thread Dan Allen



On 14 Jun 2009, at 1:27 AM, Daniel Eischen wrote:


From one of your older emails, you mention you are using
ad0s2a as / and ad0s2b as swap, and then say that ad0s2c
is unused (I may have the ad0s2 part wrong).  But ad0s2c
should be the entire slice (or partition depending on
the wording you are used to).

How about posting a relevent fdisk and disklabel (or
gpart show) so we can see what your slices and partitions
look like (fdisk /dev/ad0, disklabel /dev/ad0s2).


ad0s2c is the entire slice as you thought it should be.

Here is fdisk and bsdlabel /dev/ad0s2:

*** Working on device /dev/ad0 ***
parameters extracted from in-core disklabel are:
cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 63, size 188747622 (92161 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 10/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 188747685, size 45688860 (22309 Meg), flag 80 (active)
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 14/ sector 63
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED



# /dev/ad0s2:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a: 43591708  20971524.2BSD0 0 0
  b:  20971520  swap
  c: 456888600unused0 0 # raw part,  
don't edit



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Let's back out LOADER_ZFS_SUPPORT from STABLE

2009-06-14 Thread Dan Allen



On 14 Jun 2009, at 5:08 PM, Daniel Eischen wrote:


On Sun, 14 Jun 2009, Dan Allen wrote:


# /dev/ad0s2:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
a: 43591708  20971524.2BSD0 0 0
b:  20971520  swap
c: 456888600unused0 0 # raw part,  
don't edit


Seems weird to see swap at offset 0 and partition a after swap.
I wonder if that is screwing things up.  And shouldn't the offset
for your first slice start at offset 188747685 (from fdisk)?


Interesting insights.

I forgot to mention that there may be some discrepancies that are a  
remnant of reinstalling the OS many times.  (Now I know I could have  
used the loader.old trick...)


Anyway, while doing this a dozen times in a couple of days I learned  
that I could speed things by not doing newfs(8) each time, so the  
fsize and bsize fields are definitely messed up.  Yet things seem to  
work fine.  Weird.


My next experiment is to redo the disk entirely.

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...



On 12 Jun 2009, at 9:50 PM, Yuri Pankov wrote:


On Fri, Jun 12, 2009 at 08:24:42PM -0700, Gary Kline wrote:

Whew!! i'm giving thanks to every saint, god and daemon known.  i
rebuilt my kernel in very recent days (7.2) on my ancient
500MHz kayak, but did not go further.  So still runing on the 7.0
kernel.

Will someone send up a flare when it's *safe*?



How do you know it isn't safe? Noone hasn't provided any useful info
(debug, revisions where it works and where it doesn't).


Well, I do not think it is safe at all either.  I must have some  
strange configuration that others do not have or there would be plenty  
of people with their drives getting wiped out.


I tried removing the zfsboot and gptzfsboot items from /usr/src/sys/ 
boot/i386/Makefile and then rebuild the boot area but it once again  
killed things.


My hunch is that the boot loader is getting stuck on something strange  
about my system.


Here is my drive config, and perhaps this will cause a light bulb to  
go on for someone:


Toshiba U205, Intel 1.83GHz Core Duo, 1GB RAM, 1 120GB hard drive with  
two partitions.


The first partition is 92161 MB for Windows XP Pro.  I rarely use it.
The second partition is 22309 MB for FreeBSD.  It has 3 slices:

The first slice /dev/ad0s2a is the main 22 GB file system.
It has the / root mount point and has soft updates turned on.

The second slice /dev/ad0s2b is a 1GB SWAP partition.

The third slice /dev/ad0s2c is unused.

I will continue to test.  I am TRYING to narrow it down, it just takes  
forever.


Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...



On 11 Jun 2009, at 5:41 PM, Paul B. Mahol wrote:


Looks like boot(8) is problematic.


Okay, here is the June 13th noon update to this problem.

I once again installed a May 28th build.  Rebuilt world and kernel  
from source.  Everything works great.  No custom kernel, just GENERIC.


I then merged in just /usr/src/sys/boot/i386/libi386 changes to June  
10th.  Rebuilt in /usr/src/sys/boot and installed it, no problem.


Then I merged in the latest from /usr/src/sys/boot/i386/loader,  
rebuilt, installed, and BOOM.  DEATH TO DRIVE.  Disk label GONE  
again.  Hangs after BIOS drive C: is disk1 at boot.  Does not get to  
memory check, let alone to the Welcome to FreeBSD and choose a boot  
option screen.


CULPRIT REVEALED:
So, there is only one file change in /usr/src/sys/boot/i386/loader  
from June 8th to June 10th, which kills my machine very repeatably,  
and that is the Makefile.


Something in /usr/src/sys/boot/i386/loader/Makefile is killing my drive.

What do I try next?

Thanks for the help.

Dan
 
___

freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...



On 13 Jun 2009, at 12:50 PM, Paul B. Mahol wrote:


I doubt it is loader fault, from your description it appears that
loader is never started.

Could you try to remove -DLOADER_ZFS_SUPPORT from Makefile?


/usr/src/sys/boot/i386/loader/Makefile


BINGO!  LOADER_ZFS_SUPPORT is the culprit.

I rebuilt the good world, and brought in the loader changes which have  
caused previously caused death to my drive, then deleted the  
ZFS_SUPPORT path in /usr/src/sys/boot/i386/loader/Makefile as you  
recommended, and rebuilt things and everything works fine.


Now what do we do?

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Let's back out LOADER_ZFS_SUPPORT from STABLE


I have now proven that the recent post June 8th version of

/usr/src/sys/boot/i386/loader/Makefile

causes catastrophic data loss.

Why on earth would this change not be immediately rolled back out of  
the STABLE branch?  For those on the bleeding edge with CURRENT they  
expect to lose their entire drives, but not STABLE users.


We need to remove -DLOADER_ZFS_SUPPORT from /usr/src/sys/boot/i386/ 
loader/Makefile immediately.


Dan



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Let's back out LOADER_ZFS_SUPPORT from STABLE



On 13 Jun 2009, at 5:42 PM, Paul B. Mahol wrote:


On 6/13/09, Dan Allen danalle...@airwired.net wrote:

I have now proven that the recent post June 8th version of

/usr/src/sys/boot/i386/loader/Makefile

causes catastrophic data loss.



I hardly doubt that such change cause loss of data on entire drive.
There is always old loader to pick up.


How do I get to the old loader when the machine boots and immediately  
stops?  There is no ability at this point in the boot process to try  
and get to the old loader that I know of.  Is there a hidden magic key  
combination that allows this?


You are correct that the bulk of the file system is not touched, but  
the key file partitioning headers get cleared and when you boot off of  
a DVD -- the only way to get to the system that I know of -- and  
inspect the file partitioning via whatever means you try, it shows  
that the root partition is gone.  What was your main file system is  
gone.  I learned after many installs that I could NOT do a newfs(8)  
and the setup program would re-mark things and and files ended up re- 
appearing.


My machine was well backed up so no great loss of data in the end, but  
it has cost me lots of time to get this figured out.


For me the real questions are these:

* Why is my system the only one that this happens on?
* What makes my machine setup different?
* What is the bug in the bootable ZFS loader that munges the partition  
map?


Dan


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...

2009-06-12 Thread Dan Allen



On 12 Jun 2009, at 6:32 AM, John Baldwin wrote:


On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote:

Isn't boot part of the kernel build?  Why would installing the kernel
not cause this problem?


No, sys/boot is built during world.  Likely some change in /boot/ 
loader is
causing your problem.  Can you narrow it down to a specific change  
under

sys/boot?


Ok.  I updated just the one file since it appeared like one of the few  
changed files


/usr/src/sys/boot/i386/libi386/biosdisk.c

and rebuilt things with

cd /usr/src/sys/boot; make cleandir obj depend all install

and it was okay.  No problems.

Then I did sync'd all of the changed files for /usr/src/sys/boot and  
my machine is hung again at boot, so we have narrowed it down to  
somewhere in /usr/src/sys/boot/.


Time to reinstall from a DVD and try it with finer granularity.  This  
will take some time.


There appears to be only four files that have changed in /usr/src/sys/ 
boot from June 8th (all working fine) to June 11th (dead in the  
water).  They are:


/usr/src/sys/boot/Makefile
/usr/src/sys/boot/i386/Makefile
/usr/src/sys/boot/i386/libi386/biosdisk.c
/usr/src/sys/boot/i386/loader/Makefile

I have ruled out bisodisk.c, as stated above.

That means that the Makefiles are building new stuff that previously  
was not built, namely


zfsboot gptzfsboot

I believe it has to do with that.  More help is needed!  I am tired of  
reinstalling the OS, but I am much more paranoid about updating my  
other machine in any way now, as it could erase that whole machine.  I  
can't believe I am the only one seeing this...


Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Something since June 8th clobbers my disk...

I sync with 7-STABLE almost every day.  I build everything on a  
Toshiba U205 Satellite.  Things are fine for months on end.


I did this on June 8th.  Everything was fine.

I did this on June 10th.  The machine no longer booted.  The entire  
root partition got clobbered.  I reinstalled a snapshot of 7-STABLE  
from May 28th that I had put on a DVD.  Everything was once again fine.


I then sync'd again this morning June 11th with 7-STABLE, did a full  
build, and reproducibly, BOOM - the entire root partition got  
clobbered.  Gone.  Again.  After the reboot it just comes up with:


BTX loader 1.00  BTX version is 1.02
Consoles: internal video/keyboard
BIOS drive A: is disk0
BIOS drive C: is disk1

and stops.  Nothing else is printed.  There is no choice of how to  
boot.  There is no files for me to send, no log files to inspect, no  
remnants.  I unfortunately did not see where in the build this  
happened.  My build does the canonical steps exactly as outlined in / 
usr/src/Makefile  and then does a reboot.  It builds userland and the  
kernel.


When I inspect it from the bootable DVD the partition that my root  
filesystem was in has no association with it having the root any  
more.  The partition is listed, but it looks like it had been freshly  
partitioned.


Something is very, very wrong.

Ideas?

Dan Allen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...



On 11 Jun 2009, at 3:40 PM, Paul B. Mahol wrote:


Are you using ZFS on root partition?


No.  The disk is the default (UFS2 I believe).

So I just reinstalled BSD again and this time I did not reinitialize  
the file system and after a brief disk integrity check it reinstalled  
and files I had added were still there!


So apparently the file system did not get munged as much as the main  
disk partition map got nailed.


So, what has changed recently that could mess with the disk partition  
map?  I have Windows on the first disk partition and it has not been  
harmed with these problems.


Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...

In trying to figure this out, I rebuilt a GENERIC kernel after  
sync'ing to today's RELENG_7 sources.  I then installed it, held my  
breath, and rebooted.  It works!


So I am now looking at userland (make buildworld  make installworld)  
to see if it is the culprit.  Another possibility is my custom kernel  
build.


Stay tuned...

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...


Okay.  I did a

make buildkernel  installkernel

and rebooted, no problems.

I then did a

make buildworld

and rebooted, no problems.

I then did a

make installworld

which completed normally, rebooted, and

BINGO - my disk partition table has been zapped.

The problem appears to be something that runs during this 'make  
installworld'!


There are no problems with the build itself that I can tell, but some  
program is munging the disk partition table.


In a zany sort of way this is progress.  Of course now I have to  
reinstall the OS, again...


Dan Allen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Something since June 8th clobbers my disk...



On 11 Jun 2009, at 5:41 PM, Paul B. Mahol wrote:


Looks like boot(8) is problematic.
Anything in /etc/src.conf or /etc/make.conf?


I have never touched or created a src.conf.  If there was one there,  
it has been unmodified by me.


I HAVE modified make.conf.  Here is its contents:

--- /etc/make.conf ---

BATCH=yes
NO_PROFILE=yes
KERNCONF=DKA
USE_FORTRAN=yes
WITH_JADETEX=no
PERL_VERSION=5.8.9

---

My custom kernel named DKA has only three modifications from GENERIC:

I commented out the following three lines:

#cpu I486_CPU
#cpu I586_CPU
#makeoptions DEBUG=-g

I have run with such a kernel on many machines for many years now.

However, my experiments have shown that the kernel build is not to  
blame.


Isn't boot part of the kernel build?  Why would installing the kernel  
not cause this problem?


It is by installing the world via make installworld that my drive gets  
munged.


I obviously am missing something, but boot(8) sounds like it is in the  
neighborhood of where the problem is.


There were changes to /usr/src/sys/boot/i386/libi386/biosdisk.c and  
biospnp.c that really look suspect to me.


Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: GCC build causes panic: page already inserted

2009-03-18 Thread Dan Allen



On 18 Mar 2009, at 10:02 AM, John Baldwin wrote:


On Monday 16 March 2009 1:59:25 pm Dan Allen wrote:

I saw that someone else had this happen last week...  It is not a
hardware failure.

While building the latest GCC 4.4 from /usr/ports/lang/gcc44 I got a
core dump with the message

vm_page_insert: page already inserted

I build this port every week on a Toshiba laptop (1.8GHz Core 2  
Duo, 1
GB RAM, 160 GB HD, plenty of free space, RELENG_7).  I have never  
seen

this until today.  Just before building this port I completely built
the kernel and world and installed them, so I am as up-to-date as you
could be.

I suspect recent changes to vm code... perhaps in /usr/src/sys/vm/
vm_meter.c or vm_page.c ?

The compressed core dump is 41 MB.


When I have seen this panic on machines in the past it was caused by  
bad RAM

or another hardware problem.


Well, I have not been able to reproduce it.  I ran builds on two  
different
machines, and everything now works fine.  I will keep my eye open for  
another
occurrence, but for now we are at the end of the line on this.  At  
least I am...


Thanks to everyone for their help and ideas.

Dan


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

GCC build causes panic: page already inserted

I saw that someone else had this happen last week...  It is not a  
hardware failure.


While building the latest GCC 4.4 from /usr/ports/lang/gcc44 I got a  
core dump with the message


vm_page_insert: page already inserted

I build this port every week on a Toshiba laptop (1.8GHz Core 2 Duo, 1  
GB RAM, 160 GB HD, plenty of free space, RELENG_7).  I have never seen  
this until today.  Just before building this port I completely built  
the kernel and world and installed them, so I am as up-to-date as you  
could be.


I suspect recent changes to vm code... perhaps in /usr/src/sys/vm/ 
vm_meter.c or vm_page.c ?


The compressed core dump is 41 MB.

Dan



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: GCC build causes panic: page already inserted



On 16 Mar 2009, at 1:01 PM, Alan Cox wrote:


For now, can you just provide the stack trace?


How do I do this?  Is there a tool that I run against the core dump?

BTW, I just did the same gcc-4.4 build on my Mac and it built fine  
without any core dumps...


Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: GCC build causes panic: page already inserted



On 16 Mar 2009, at 3:42 PM, Patrick Lamaizière wrote:


Le Mon, 16 Mar 2009 14:49:43 -0600,
Dan Allen danalle...@airwired.net:


For now, can you just provide the stack trace?


How do I do this?  Is there a tool that I run against the core dump?


See
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html

Regards.


Thanks!

It turns out that one must have a debug kernel around.  I use STABLE  
as a production system.  There is no kernel.debug on my system.  I  
guess I therefore cannot provide a stack trace.


Sorry.

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: GCC build causes panic: page already inserted



On 16 Mar 2009, at 1:01 PM, Alan Cox wrote:


For now, can you just provide the stack trace?


As I mentioned, I am unable to do so - I have no kernel.debug.

However, I am trying to reproduce the bug again.  (It takes a while.)   
Although it has not yet crashed, I noticed another unusual behavior:


Normally during my gcc builds the 1 GB of swap space is never  
touched.  My main 1 GB of RAM is sufficient and there is always at  
least 100 MB of free memory.


Today I saw a STATE listed when running top that I have never seen,  
called wdrain.  This happened when I saw my free memory plummet down  
to only 20 MB free (out of 1 GB).  This state appears to be set in / 
usr/src/sys/kern/vfs_bio.c in a routine called waitrunningbufspace().   
This file also was modified March 1st.  I do not know if there is a  
connection...


The last time I built gcc-4.4 was probably just before this.  (I build  
gcc whenever there is a new version, within a couple of days of it  
being added to ports.  There was about two weeks with no new versions  
this first half of March so it has been a couple of weeks...)


I am tempted to go back to about Feb 28th kernel-wise and try the gcc  
build again and see if it works or panics.


Any suggestions as to how I can help narrow this down?

Dan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: x48 display messed up with Xorg 7.4

2009-02-12 Thread Dan Allen


On Wed, 11 Feb 2009 19:29:57 +0200, Esa Karkkainen wrote:

I've got screenshots at:
http://koti.welho.com/ekarkkai/x48_snap_1.jpg
http://koti.welho.com/ekarkkai/x48_snap_2.jpg


Those look exactly like the problem I am having.
So, what piece of Xorg causes display problems?  Graphics drivers,  
right?

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

x48 display messed up with Xorg 7.4

2009-02-10 Thread Dan Allen

One of my favorite little apps is the HP48 calculator emulator called  
x48.


In the recent upgrade to Xorg 7.4 the screen on the calculator is  
completely screwed up - nothing appears as it should.


I am on a Toshiba Satellite U205 with Intel i810 graphics running 7.1- 
STABLE.


I did manage to get Firefox working on 7.4, but this graphics issue  
still was there so I went back to Xorg 7.3 and everything works again.


Has anyone else seen this?

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Unhappy Xorg upgrade

2009-01-29 Thread Dan Allen


Thanks to Robert for pointing out a few things to me.

I have run

portupgrade -rf libxcb

and it rebuilt quite a few pieces that had not been rebuilt in the  
standard portupgrade that gave me X.org 7.4 in the first place.


After rebuilding firefox and a bunch of smaller libraries, my keyboard  
and mouse work, and so does firefox and my other apps.


Thanks to everyone else for emailing me with ideas and suggestions!

Dan
 
 
___

freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Unhappy Xorg upgrade

2009-01-28 Thread Dan Allen


While this enabled the mouse (without HAL), it did nothing good about:

   a. The bogus keyboard scans.

Everyone is talking about an xorg.conf
The new X.org 7.4 upgrade hit me too: no keyboard  no mouse!  Bummer.
I found that if I simply added to /etc/rc.conf:
  hald_enable=YES
that things now work for me.
Previously I never have had hald in my rc.conf.
Hope this helps.
Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Unhappy Xorg upgrade

2009-01-28 Thread Dan Allen

Although the hald_enable in /etc/rc.conf worked, I noticed that a lot  
of other demons get running.  I needed to add dbus_enable as well.   
That fix is too intrusive in my book.


In any event Firefox is now broken and does not run at all.

I backed out the /etc/rc.conf changes and generated an xorg.conf by  
calling Xorg -configure.  I moved this to /etc/xorg.conf.  Things were  
still broken until I added the recommended


Option AllowEmptyInput off

in the ServerLayout section of xorg.conf.

Now I can use X again BUT... Firefox 3.0.5 is still broken.  It has  
worked fine until this new Xorg.


This 7.4 version of X.org is not ready for STABLE!

Dan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: make buildkernel fails

2009-01-22 Thread Dan Allen


=== umass (all)
/usr/src/sys/modules/umass/../../dev/usb/umass.c:577: error:  
'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function)
/usr/src/sys/modules/umass/../../dev/usb/umass.c:613: error:  
'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function)

*** Error code 1
I got this same error but after syncing just now to get a new /usr/src/ 
sys/dev/usb/usbdevs file the build once again succeeds.


Dan



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Missing fstab

2008-09-29 Thread Dan Allen

In messing around trying to get a bootable FreeBSD system on a memory  
stick I messed up and deleted my fstab file on my main FreeBSD STABLE  
machine.  Actually a script I was writing overwrote it...  arrggghh.


I feel so stupid.

Anyway, my system now boots and then dies midway in boot because there  
is no /etc/fstab.  I get the mountroot prompt, I type in ufs:ad0s2a  
(my main root partition) and it begins booting fine.  So far so good.


It then goes into single user mode, which is fine, but it leaves my  
main root filesystem as readonly, which is not so fine. This is  
because of the missing /etc/fstab file.


I have a backup of my fstab file on a USB memory stick.  I can mount  
the stick on /mnt and then I type


/sbin/mount -F /mnt/fstab -f -u -w /

thinking that it will now update the drive to readwrite.  It does  
not.  The command appears to succeed but running mount again shows the  
file system is still read-only.  It will not mount my main root file  
system readwrite.  I believe my main file system is fine.  I can see  
all of my files readonly.


I cannot change my root file system in order to copy my backup fstab  
back to /etc/fstab because the file system refuses to be updated to  
readwrite.  This is my core problem.


fsck will not run because there is no /etc/fstab and there is no  
option that I can find that will allow a different fstab to be used,  
although running fsck is not my central problem.


Any ideas on how to force the file system to be readwrite long enough  
for me to replace my /etc/fstab file?


Dan



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

Re: Missing fstab

2008-09-29 Thread Dan Allen



On 29 Sep 2008, at 11:11 AM, Sean Bruno wrote:


A mount -o rw /dev/ad0s1a / doesn't just work for you?


It didn't, but when you said this I tried something else.

I went directly into single user mode myself (option 4 at boot) and  
THEN I tried this and IT WORKED!


Apparently when the system dies in the middle of processing rc.d and  
then it puts you into single user mode, you are left in a weird state  
that these commands would not work in.


Thanks!

Dan

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

Re: Inspiron 1525 Hardware

2008-09-07 Thread Dan Allen



On 7 Sep 2008, at 7:57 PM, Daniel O'Connor wrote:

You need a 'real' serial port for console, the other option would be  
to

use Firewire (if the laptop has it).


The Dell Inspiron 1525 DOES have a mini-Firewire port on the front of  
the machine.


Dan


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

Re: Inspiron 1525 Hardware

2008-09-06 Thread Dan Allen



On 5 Sep 2008, at 9:43 PM, Jeremy Chadwick wrote:


I cannot find a single PCI/PCIe card that uses the 88E8040.


I wonder how Ubuntu supports this ethernet chip?  It is amazing that  
only two Dell's use this chip.  Maybe it is not worth worrying about  
after all...


Don't kill yourself over this.  It is not the end of the world.  It  
appears I will be able to get my Intel 4965 Wireless working in which  
case I can use that.  I have lots of computers in which I can run  
FreeBSD.


Dan

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

Re: FreeBSD 7.1 Content



On 4 Sep 2008, at 7:43 AM, Wesley Shields wrote:

No thanks.  This means you have to have a working connection to  
install
firefox via this method.  Since not everyone will have that it is  
still
necessary to bundle the firefox package on the media, bringing us  
right

back to the very issue you are trying to solve.


No.  You do NOT get my point.  Firefox is (almost) worthless without  
an internet connection.  It's whole purpose is to browse the  
internet.  Therefore, if you are going to use firefox, you by  
definition have an internet connection, hence you have the ability to  
get firefox through this same internet connection.  (This assumes  
fetch or wget or curl is around to get firefox.)


Dan



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

Re: FreeBSD 7.1 Content



On 4 Sep 2008, at 12:20 AM, Jeremy Chadwick wrote:


I haven't finished reading the thread yet, but your assumption is
ignorant.  Why do you think FreeBSD is intended solely for desktop
usage?  It's not.

I, for one, **only want a command prompt** out of the box.  I **do  
not**

want Xorg or any X-related garbage on my servers.


Jeremy - read the whole thread first.  My assumption is NOT ignorant.

I know that most people want just a command prompt.  I myself live in  
command prompt mode on FreeBSD most of the time as well.  I completely  
agree with you that there are many times when I do not want X.org  
anywhere around.  I get that many people consider FreeBSD a server  
OS.  I often tell people about how Yahoo and other big sites run on it.


You may be interested to know, however, that some people ALSO use it  
as a desktop system. ;-)


This is not trying to force anyone to have Firefox or Xorg.  This is  
about options in the FreeBSD installer that USED to allow the OPTION  
of having X setup for you.  This is about OPTIONS to install the  
single most widely used kind of software (a web browser) on the system  
in a simple, straightforward way.


In the Standard Install there should be an option that says Install  
Firefox  Xorg.  It should be an OPTIONAL CHECK BOX, not a mandatory  
one, but it should allow a desktop scenario to be setup easily.


If the disks are near full, or need to be uniform across processors,  
or whatever, then I am okay with not having all of X and Firefox on  
disc1 IF there was a simple set of pkg_add -r commands that could  
hidden behind a script or dialog which could fetch the necessary  
software over the internet and set it up (along with .conf files so X  
starts up reasonably well) so that a non-command line user could have  
a good first time experience.


It was using Ubuntu that caused me to realize how far behind FreeBSD  
is on the desktop side, and how, with a SMALL AMOUNT of work and  
changes, it could make a big jump forward by this proposed simple  
addition.  Heck, if nothing else the installer could simply say in a  
help screen, if you want a web browser on your system, type 'pkg_add - 
r firefox' on your system and edit blah blah .conf blah.  As it  
stands right now, however, there is very little in the install process  
which helps a user get X up and going with a browser.


Thanks to everyone else for their comments.

Dan



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

Re: FreeBSD 7.1 Content



On 4 Sep 2008, at 3:42 AM, Oliver Peter wrote:


On Wed, Sep 03, 2008 at 02:58:45PM -0600, Dan Allen wrote:


On 3 Sep 2008, at 1:14 PM, Peter Jeremy wrote:


Your patches to add support for the i4965 and your Marvell 88E80xx
must have been stripped by the mailing list software.  Can you  
please

re-send them.


I have not written patches, thus I did not send any patches.


|
`--  http://en.wikipedia.org/wiki/Sarcasm

Btw. my philosophy is if you would like to use your favourite open  
source
operating system - which I guess is FreeBSD - on your new hardware,  
you
should spend additional 15 minutes when you make the decision what  
hardware

you are going to buy and check the specs with the Hardware Notes at
http://www.freebsd.org/where.html.

Complaining afterwards is easy but no one forces you to buy  
unsupported

hardware.


Point taken.  A $500 Dell laptop, however, will be a popular machine  
and sooner or later should be supported.


You know I thought you were being sarcastic, but then I was not sure...

Dan

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

Re: FreeBSD 7.1 Content



On 4 Sep 2008, at 8:22 AM, Jim Pingle wrote:


The CD installs are great for me, and have worked well for years.
Personally, I install, update to -STABLE from a local cvsup mirror,  
then use
an updated ports tree or install packages remotely. The packages on  
CD are
out of date practically from the moment they are placed there, so I  
rarely
use them. The only package I regularly used was cvsup-without-gui,  
which has

been replaced by csup in the base system.


Okay, so how about for packages on the base CD:

* cvsup-without-gui (I also always use this)
* rsync
* perl

Then, since packages are always out-of-date, why not just skip the DVD  
and use the internet with a couple of check boxes at the end of the  
install, the way ports is treated now, that are just calls to pkg_add - 
r for:


* KDE
* GNOME
* Firefox
* ... whatever else are the most popular add-ons

Fewer bits to be delivered via CD/DVD, and things are always up-to-date.

Also, is not Ubuntu a downstream release of Debian, much like  
FreeSBIE and
PC-BSD are downstream of FreeBSD? If you want to compare apples to  
apples,

you might investigate those choices a little closer.


Touche.  I had forgotten this.  Perhaps this is why I was able to  
crash Ubuntu so quickly yesterday... ;-)


I hope everyone realizes that I am not trying to de-server FreeBSD.   
I just remember how daunting it was for me to get X setup when all I  
wanted to use was a web browser when I was new to it all.


The early BSD releases had a simple check box to add X support and it  
all just worked.  That was COOL.  That is what I am hoping to get back  
into BSD.


I do not want to spill onto DVDs, remove the sources, get rid of  
command prompts, or force systems to have X.org on them...


Dan

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

Inspiron 1525 Hardware



On 3 Sep 2008, at 1:14 PM, Peter Jeremy wrote:


A large number of Marvell 88E80xx chips are supported by msk(4).  If
yours isn't, you are going to need to provide more details on what
chip you have.



On 3 Sep 2008, at 7:02 PM, Aragon Gouveia wrote:


lspci ?


I ran the lspci command and it states that the Ethernet is a Marvell  
88E8040 PCI-E Fast Ethernet Controller.  Are you looking for more info?


Here is what lspci on Ubunut returns:

Slot:   00:00.0
Class:  Host bridge [0600]
Vendor: Intel Corporation [8086]
Device: Mobile PM965/GM965/GL960 Memory Controller Hub [2a00]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:0c

Slot:   00:02.0
Class:  VGA compatible controller [0300]
Vendor: Intel Corporation [8086]
Device: Mobile GM965/GL960 Integrated Graphics Controller [2a02]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:0c

Slot:   00:02.1
Class:  Display controller [0380]
Vendor: Intel Corporation [8086]
Device: Mobile GM965/GL960 Integrated Graphics Controller [2a03]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:0c

Slot:   00:1a.0
Class:  USB Controller [0c03]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) USB UHCI Controller #4 [2834]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   00:1a.1
Class:  USB Controller [0c03]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) USB UHCI Controller #5 [2835]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   00:1a.7
Class:  USB Controller [0c03]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) USB2 EHCI Controller #2 [283a]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02
ProgIf: 20

Slot:   00:1b.0
Class:  Audio device [0403]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) HD Audio Controller [284b]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   00:1c.0
Class:  PCI bridge [0604]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) PCI Express Port 1 [283f]
Rev:02

Slot:   00:1c.1
Class:  PCI bridge [0604]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) PCI Express Port 2 [2841]
Rev:02

Slot:   00:1c.4
Class:  PCI bridge [0604]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) PCI Express Port 5 [2847]
Rev:02

Slot:   00:1d.0
Class:  USB Controller [0c03]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) USB UHCI Controller #1 [2830]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   00:1d.1
Class:  USB Controller [0c03]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) USB UHCI Controller #2 [2831]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   00:1d.2
Class:  USB Controller [0c03]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) USB UHCI Controller #3 [2832]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   00:1d.7
Class:  USB Controller [0c03]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) USB2 EHCI Controller #1 [2836]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02
ProgIf: 20

Slot:   00:1e.0
Class:  PCI bridge [0604]
Vendor: Intel Corporation [8086]
Device: 82801 Mobile PCI Bridge [2448]
Rev:f2
ProgIf: 01

Slot:   00:1f.0
Class:  ISA bridge [0601]
Vendor: Intel Corporation [8086]
Device: 82801HEM (ICH8M) LPC Interface Controller [2815]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   00:1f.1
Class:  IDE interface [0101]
Vendor: Intel Corporation [8086]
Device: 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller [2850]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02
ProgIf: 8a

Slot:   00:1f.2
Class:  IDE interface [0101]
Vendor: Intel Corporation [8086]
Device: 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller [2828]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02
ProgIf: 8f

Slot:   00:1f.3
Class:  SMBus [0c05]
Vendor: Intel Corporation [8086]
Device: 82801H (ICH8 Family) SMBus Controller [283e]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:02

Slot:   02:09.0
Class:  FireWire (IEEE 1394) [0c00]
Vendor: Ricoh Co Ltd [1180]
Device: R5C832 IEEE 1394 Controller [0832]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:05
ProgIf: 10

Slot:   02:09.1
Class:  SD Host controller [0805]
Vendor: Ricoh Co Ltd [1180]
Device: R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [0822]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:22
ProgIf: 01

Slot:   02:09.2
Class:  System peripheral [0880]
Vendor: Ricoh Co Ltd [1180]
Device: R5C843 MMC Host Controller [0843]
SVendor:Dell [1028]
SDevice:Unknown device [022f]
Rev:12

Slot:   02:09.3
Class:  System peripheral [0880]
Vendor: Ricoh

Re: FreeBSD 7.1 Content



On 4 Sep 2008, at 9:42 AM, Randy Pratt wrote:


2 FTP  Install from an FTP server


We have a winner!  I think this is what I may have overlooked: setting  
the source to FTP rather than to CD.


I have always used the packages on the discs, and I have always  
downloaded just disc1, which used to include some of the packages  
being discussed, such as X.


Dan



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

Re: FreeBSD 7.1 Content



On 4 Sep 2008, at 9:49 AM, Jim Pingle wrote:

My memory may be failing me, but there used to be a port called  
instant
workstaion that accomplished quite a bit, and the installer would  
drop in X
but asked for KDE or Gnome, but I don't recall when those choices  
went away.


This is in fact what I remember too: one had a choice of Server or  
Workstation and a further choice of KDE or GNOME.  I remember that  
when I saw the choice of KDE or GNOME I had no idea which I should  
choose because I knew nothing about them.


I will re-explore these sysinstall options, and grabbing packages with  
FTP once I can figure out how to get some sort of networking going on  
my new laptop.


Dan



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

Re: Inspiron 1525 Hardware



On 4 Sep 2008, at 10:29 AM, Gavin Atkinson wrote:


This is supported by the iwn(4) driver in CURRENT, and it should be
quite easy to port the driver to 7-STABLE.  If you're interested in
reinstalling FreeBSD and testing a backported driver, I'm sure this  
can

be sorted.


I am interested in doing this.  Please advise on how I can get these  
bits.


Dan

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

FreeBSD 7.1 Content


BACKGROUND:

A few years ago one could get a FreeBSD CD and install X and get a  
decent basic system from one CD.


One can still do this with Ubuntu today as well.

Why can't we have a small window manager like icewm along with Firefox  
3.0+ be among the packages on the first FreeBSD CD so a basic working  
system with a web browser can be a default install?  Is it that X.org  
is now too big?


I have been a FreeBSD user/builder for more than a decade because of / 
usr/src/make - complete sources and a beautiful build system, but I  
must admit that Ubuntu has done a great job of modern hardware  
detection and providing a nice useable system out of the box.  I wish  
we could join both worlds in a future BSD release.  (I crashed Ubuntu  
8.04 in the first day so I still prefer BSD to Linux.)


Also, and I am sure I am not the only one with one of these, my new  
$500 Dell Inspiron 1525 is not supported well by BSD RELENG_7: the  
Intel 4965 wireless and the Marvell 88E80xx Ethernet are both NOT  
supported so I have a great new laptop which cannot connect to the  
outside world with BSD.  :-(  Ubuntu supports these and lots more.


SUMMARY:

I would like to see FreeBSD 7.1 add to its disc1:

1) X.org
2) icewm
3) firefox-3.0
4) support for Intel 4965 wireless drivers
5) support for Marvell 88E8040 ethernet driver

Dan Allen

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

Re: FreeBSD 7.1 Content



On 3 Sep 2008, at 1:14 PM, Peter Jeremy wrote:


Your patches to add support for the i4965 and your Marvell 88E80xx
must have been stripped by the mailing list software.  Can you please
re-send them.


I have not written patches, thus I did not send any patches.

Dan

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

Re: FreeBSD 7.1 Content



On 3 Sep 2008, at 1:53 PM, Guido Falsi wrote:

If you just want na instant workstation, why you just don't try  
Freesbie or something like that?


Because I want something from the source -- from the main team -- and  
not something downstream.


If I install FreeBSD on a PC I expect this installation to live  
there for some years. I can spend some hours/days installing and  
configuring what I really need. At least this is the way I see it.  
Maybe I'm misunderstanding you.


I too spend the time.  I am thinking that for other people to want to  
use FreeBSD they want something other than a command prompt.  They at  
least want a web browser out of the box.


The Ubuntu install is very compelling.  I am just wishing that FreeBSD  
was AS compelling in its first install experience.  At present it is  
far, far behind.


That does not stop ME from preferring FreeBSD, but it stops many other  
people.


Dan


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

Re: FreeBSD 7.1 Content



On 3 Sep 2008, at 1:58 PM, Wesley Shields wrote:


I installed the June snapshot of -current on my laptop and it supports
my Intel 4965 just fine.  Support for this card is out there and does
work, just not in RELENG_7.


On 3 Sep 2008, at 2:45 PM, Gavin Atkinson wrote:


There is support for the Intel 4965 in HEAD, with the iwn(4) driver.


Thanks guys for the info.

Not having ANY wired or wireless support in FreeBSD for a very decent  
Dell laptop that is flying off of the shelves at $500, I deleted  
FreeBSD from the machine and installed Ubuntu 8.04.  I therefore  
cannot run pciconf -l at this moment in time, but I may get back  
around to it.


Stay tuned... maybe for 7.2.

Dan

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

Re: FreeBSD 7.1 Content



On 3 Sep 2008, at 1:14 PM, Peter Jeremy wrote:


Disc1 is full.  What do you suggest should be removed from disk1 to
make space for the above?


I see.  I was thinking of FreeBSD 7.0 whose disc1 is 509 MB in size,  
leaving almost 200 MB free for a standard 700 MB CD.


Q: Has FreeBSD 7.1 REALLY filled up 189 MB with bug fixes and new  
hardware support?


Ubuntu 8.04 has room for the linux kernel, for GCC, for tons of  
packages including almost all of OpenOffice 2.2.1 (which is HUGE),  
GIMP, Firefox, X of course, and quite a few other things on their 700  
MB CD, including support for lots of new hardware that BSD does not  
have.


BSD has source code -- which I personally would rather have than GIMP,  
etc. -- but do the sources take up that much room?  They take 70-80  
MB, but the bulk of that is already included in the above 509 MB of  
7.0 disc1.  (BTW, having full sources as part of FreeBSD is in my  
opinion one of the coolest features of BSD so that should NEVER be  
compromised.)


So, I where the BSD free space is going??

Here is a quick list (not exhaustive or definitive) of the libraries  
that Firefox 3.0 requires, and their sizes in bytes:


3969firefox
8332firefox-bin
1080753 libX11.so.6
9564libXcomposite.so.1
40524   libXcursor.so.1
9040libXdamage.so.1
64848   libXext.so.6
18716   libXfixes.so.3
37019   libXi.so.6
9279libXinerama.so.1
26618   libXrandr.so.2
35933   libXrender.so.1
132271  libatk-1.0.so.0
478869  libcairo.so.2
204002  libfontconfig.so.1
341460  libfreebl3.so
514577  libfreetype.so.9
603150  libgdk-x11-2.0.so.0
102751  libgdk_pixbuf-2.0.so.0
760129  libglib-2.0.so
13540   libgmodule-2.0.so.0
251326  libgobject-2.0.so.0
3930035 libgtk-x11-2.0.so.0
592012  libmozjs.so
238383  libnspr4.so.1
1140648 libnss3.so
324468  libnssckbi.so
113912  libnssdbm3.so
86560   libnssutil3.so
262000  libpango-1.0.so.0
37947   libpangocairo-1.0.so.0
163539  libpangoft2-1.0.so.0
213877  libplc4.so.1
209648  libplds4.so.1
145260  libsmime3.so
210076  libsoftokn3.so
409876  libsqlite3.so
180320  libssl3.so
13296   libxpcom.so
14678048 libxul.so

These total 27696575 bytes or 26.4 MB.  Notice this includes some of X  
(but I am sure some of these libraries include other libraries that  
are not included in this total.  This is not a full DAG analysis.)   
Firefox also links to libc, libz, libm and other common libs, but they  
are part of the base system so they are not on this list.


Compressed using tar czpf (gzip) these files occupy 11003400 bytes or  
10.5 MB.


Compressed using tar cjpf (bzip) these files occupy 10124743 bytes or  
9.7 MB!



Dan



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

Re: FreeBSD 7.1 Content



On 3 Sep 2008, at 3:11 PM, Steven Hartland wrote:

- Original Message - From: Dan Allen [EMAIL PROTECTED] 



I too spend the time.  I am thinking that for other people to want  
to  use FreeBSD they want something other than a command prompt.   
They at  least want a web browser out of the box.


For some, but for others like ourselves here we really don't want all
that bloat. One of the reasons we really like it is its perfect for
server installs, no crap installed that you don't want :)


Agreed, but if you go back to earlier versions of FreeBSD they gave  
you an install option for just binaries, or binaries + sources, or  
binaries + sources + X Windows.


I am proposing something similar once again, but this time if would be  
enough of X, a small window manager, and Firefox so a basic windowing  
environment was able to be installed, from the CD, with a single  
choice.  I doubt many developers are really browsing the web all day  
with lynx.


Dan

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

Re: FreeBSD 7.1 Content


Phillip Salzman wrote:
An easy answer would be to put the web-browser and such the first  
disk, but
I don't think it would solve anything.  If it kept with those,  
FreeBSD would
find itself just moving towards the same work being done at PC-BSD,  
wouldn't

it?


When I see almost 200 MB free on disc1 of 7.0, and I remember the  
handy apps  pkgs which used to be on past releases of FreeBSD, I do  
not see it as moving towards PC-BSD as much as I see it as going back  
to what FreeBSD used to have just a few releases ago.
In truth, for workstations and laptops at least, most of us do want a  
web browser.  Not having a decent web browser out of the box in 2008  
after 15 years of web browser development gives BSD a really archaic  
look and feel.  We all know that BSD is the best, most solid OS out  
there - but occasionally we need to do a bit of marketing, we need to  
show our stuff to let others see that we get it.

Dan

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

Re: FreeBSD 7.1 Content



On 3 Sep 2008, at 4:58 PM, Guido Falsi wrote:

Also, FreeBSD is still a little download compared to other systems.  
I would not like to download a multiGB distribution when what I need  
is just base system + sources, to build everything up from there.


I do not want to download a big multi GB distro either.

If you however could see how much cool stuff Ubuntu has in their  
single CD, you would be very impressed.  (See my earlier mail.)


We can do much better.

Dan

PS - back in the BSD 4.0-5.0 timeframe rc.conf got setup by the  
installer for you so that you could get X up and going without much  
hassle at all.





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

Re: FreeBSD 7.1 Content



On 3 Sep 2008, at 5:36 PM, Scott Long wrote:


What's wrong with downstream?


I can crash most Linux distributions in an hour.  Your examples are  
just why I like FreeBSD and why I do not like or normally use Linux.   
I only grabbed Ubuntu recently because there is ZERO net access from  
FreeBSD on my new Dell laptop.


Linux to me is too random.  FreeBSD has always appealed to me because  
it has a higher quality bar, more structure to it (like /usr/src/ and  
its sweet buildworld), and it does not include every possible gadget  
in it.  I know that my proposing the addition of Firefox to disc1 may  
be seen as every possible gadget but having a web browser is pretty  
important these days.



Having derivative releases like FreeSBIE and PCBSD and others is an
excellent way to make the release process scalable and able to meet  
the
wants and needs to different users, yourself included.  In fact, I  
think
it's an utter waste of time for the FreeBSD release team to worry  
about

packages on disc1 and whatnot.  That needs to be done by teams who can
focus on doing that task and doing it well.  The FreeBSD releases need
to become bare-bones references for others to build on an repackage  
and

grow and improve.  That's already started, but the efforts of those
teams needs to be highlighted and given more, dare I say it, respect.
They are the future that will bring FreeBSD to a wider audience.  They
need to be treated as first-class developers and members of the  
FreeBSD

family; the official freebsd.org releases need to relegated to being
just bare-bones bits that are there for others to bring to the masses.


You have good arguments here.  You state -- very correctly -- that  
derivative release teams need to be treated as first-class developers  
and members of the FreeBSD family.


But are they treated so?  Can larger audiences of developers be  
entertained while maintaining FreeBSD's stability?


FreeBSD has as one of its great strengths a small set of developers  
and a release process that seems to deliver a more reliable product  
than Linux, at least in my experience.  The fewer people that mess  
with the bits, the more stability delivered.  Obviously the other side  
of the coin is that if not enough people mess with the bits then not  
enough features and hardware support will exist and the product will  
be irrelevant.


Finding the sweet spot is hard.

If derivative release teams are modeled after FreeBSD core -- good  
checkin structure, a few solid contributors rather than teaming hordes  
of inexperienced programmers -- then perhaps that is the way to go.   
If they do not have the structure, process, and experience, then it  
should be done by the mainline team.


For me, as long as ANY packages are shipped on disc1, then I think  
they should be the right ones, and my hunch is that there should be  
just a few packages and their dependencies: rsync, perl and firefox.   
Firefox of course will drag in a bunch of stuff (X.org,atk,gtk...).   
(Actually rsync should become part of the main distro.  It is so  
incredibly useful, but that is just one man's opinion.)


This is a good dialog to have.  I do not know if this is the right  
list for it, and I certainly do not want to mess up 7.1.  Perhaps none  
of this can be ironed out in time for 7.1 and it will have to wait for  
7.2.  That is fine.


Whose job is it to decide on the packages for a release?  I have spent  
a non-zero amount of time looking for specifications or design plans  
for releases and have been unable to find them.


Thanks to everyone today for your comments!

Dan



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

Re: FreeBSD 7.1 Content