On Sun, 4 Jun 2006, Gary Palmer wrote:
> On Sat, Jun 03, 2006 at 11:35:29PM -0400, Brian Tao wrote:
> > errno 8 is ENOEXEC and 13 is EACCES... but:
>
> Silly question: /sbin/init has the "x" flag set, correct? It should be
> mode 0500 (i.e. -r-x--)
Yep...
# ls -ld / /sbin /sbin/init
On 6/3/06, doug <[EMAIL PROTECTED]> wrote:
Unless you have a reason to want to modify the source, why not use the
package:
setenv PACKAGEROOT ftp://ftp.FreeBSD.org
pkg_add -r xorg
will get you 6.9.0_1 in a few minutes
There have been updates released after it was released - nothin
On Sat, Jun 03, 2006 at 11:35:29PM -0400, Brian Tao wrote:
> errno 8 is ENOEXEC and 13 is EACCES... but:
Silly question: /sbin/init has the "x" flag set, correct? It should be
mode 0500 (i.e. -r-x--)
___
freebsd-stable@freebsd.org mailing list
h
On Sat, 3 Jun 2006, Doug White wrote:
>
> 1. Capture the boot output from both the working 6.0 kernel and your
> broken 6.1 kernel and compare the two. If there are differences or errors
> being returned from the ATA controller or disks then those will need to be
> addressed.
My serial console
On Sat, 3 Jun 2006, Doug White wrote:
>
> This is usually indicative of bad RAM or a faulty processor. Since
> you seem to be having disk problems, it may just be due to the disk
> returning faulty data. Or there is a bad kernel module in the mix
> that is randomly corrupting data.
Thanks for
thanks - I appreciate the feedback
On Sat, 3 Jun 2006, Doug White wrote:
> On Fri, 2 Jun 2006, [EMAIL PROTECTED] wrote:
>
> > My system works, however the buildkernel process had about 2000
> > warnings, with 1/2 of those compiling aic7xxx (see below). This was
> > discussed on BSDForums but as f
On Fri, 2 Jun 2006, [EMAIL PROTECTED] wrote:
My system works, however the buildkernel process had about 2000
warnings, with 1/2 of those compiling aic7xxx (see below). This was
discussed on BSDForums but as far as I can tell, different compiler
options were used; the conclusion was using -O3 w
On Sat, 3 Jun 2006, Brian Tao wrote:
I had a very stable 6.1-R amd64 server (once I swapped out some
bad RAM, that is) that needed a couple more hard drives installed.
There were some problems with the upgrade (device renumbering woes,
basically... topic of another thread), and it had to be
On Tue, May 30, 2006 at 09:12:21PM +, Arno J. Klaassen wrote:
> mount option is unknown
> May 31 01:54:18 accuracy mountd[443]: can't delete exports for
> /users/angora/u4: Invalid argument
Can you update RELENG_6, and rebuild the kernel and world?
I merged some more fixes from CURRENT
I had a very stable 6.1-R amd64 server (once I swapped out some
bad RAM, that is) that needed a couple more hard drives installed.
There were some problems with the upgrade (device renumbering woes,
basically... topic of another thread), and it had to be rolled back.
Upon rolling back, th
On Friday 02 June 2006 16:04, Dan Pelleg wrote:
> > You should also consider upgrading to FreeBSD 6.x, as a lot of
> > improvements were made to the wireless stack, over an above the
> > improvements in 5.4/5.5.
> >
> > > [EMAIL PROTECTED]:14:0:class=0x02 card=0x3a681186
> > > chip=0x0
UP FreeBSD 6.1-STABLE #0: Fri Jun 2 13:44:52 EEST 2006
-- cut here --
(kgdb) bt full
#0 doadump () at pcpu.h:165
No locals.
#1 0xc0579530 in boot (howto=260) at ../../../kern/kern_shutdown.c:409
first_buf_printf = 1
#2 0xc0579ac3 in panic (
fmt=0xc0744d44 "vm_page_unwire: invalid wi
On Sat, Jun 03, 2006 at 10:48:43AM +1000 I heard the voice of
Antony Mawer, and lo! it spake thus:
>
> ... but there have been a huge number of commits over the recent few
> years.
I believe the actual culprit is GEOM tasting (or trying to taste) the
media, and not getting the message that there
Unless you have a reason to want to modify the source, why not use the package:
setenv PACKAGEROOT ftp://ftp.FreeBSD.org
pkg_add -r xorg
will get you 6.9.0_1 in a few minutes
On Sat, 3 Jun 2006, Kaiwai Gardiner wrote:
On 6/3/06, Manfred Lotz <[EMAIL PROTECTED]> wrote:
Hi,
BTW, I'm ru
14 matches
Mail list logo
