> No rain here, it is ARG_MAX - 2048:
> -s size
> Set the maximum number of bytes for the command line length pro-
> vided to utility. The sum of the length of the utility name and
> the arguments passed to utility (including NULL terminators) will
>
Hi!
I'm trying to upgrade from 3.0 to 4.3 but make buildworld fails
cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused
-Wmissing-prototypes -Wredundant-decls
-I/usr/obj/usr/src/i386/usr/include -static -o config config.o main.o
lang.o mkioconf.o mkmakefile.o mkheaders.o mkoptions.o -ll
On Mon, Apr 23, 2001 at 01:58:05PM +0200, Mart Norman wrote:
> Hi!
>
> I'm trying to upgrade from 3.0 to 4.3 but make buildworld fails
Why are you sending this to freebsd-current?
> Any hints what should i do to make buildworld successful?
Do a binary upgrade; it will be much easier.
Kris
P
Rodney W. Grimes <[EMAIL PROTECTED]> wrote:
> > Before anyone starts writing scripts, consider that {} will be
> > replaced by xargs with (roughly) ARG_MAX - 10 characters worth of the
> > stuff coming off the pipe. If your combined arguments plus
> > environment exceeds ARG_MAX execve(2)
[-current from 04/21 ]
After I upgraded from a current dated approx 04/15 to current from
04/21, my movemail stopped working on NFS mounted partitions (i use
XEmacs and VM for mail). I tested it out and it works fine on local
partitions.
My normal NFS server is a FreeBSD 3.4-stable box. I also
Since client side locking was implemented, I am having much trouble
reading mail on an NFS-mounted mail spool.
The NFS server is a Solaris 2.6 U250, and I am reading mail using mutt.
When lockd is not running, mutt gets EOPNOTSUPP when trying to flock().
When lockd is running, it occasionnally g
Hello all,
I've just made cvsup to -current and when I try to recompile my kernel I get the
following error message:
-c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W
missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -an
si -nostdinc -I-
IF you run -current you are expected to follow both this list and the
cvs-all list. Your answer is there.
User & wrote:
>
> Hello all,
>
> I've just made cvsup to -current and when I try to recompile my kernel I get the
>following error message:
>
> -c -O -pipe -Wall -Wredundant-d
On 22-Apr-01 David O'Brien wrote:
> On Mon, Apr 16, 2001 at 08:10:39PM -0700, John Baldwin wrote:
>> Also, Bruce's fix is not entirely correct as it breaks for the
>> non-debug kernel case, but I've already sent you a mail about that,
>> just to let everyone know that it should be fixed shortly.
Hello,
After some feedback, I have changed the patch slightly. Rename
-d to -t and remove the requirement for the option to have a
value.
-t aquire the target from *argv++ instead of argv[argc--]
The patch can be found at:
http://people.freebsd.org/~jwd/cp-t.patch
Some comments:
I just received this error in the kernel compile in
/usr/home/src/sys/modules/linux.
My CVS tree was updated immediately before kernel compile (approx. 2:45pm
CST).
cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
In message <[EMAIL PROTECTED]> John Baldwin writes:
: You need to rebuild fsck and install it and fsck your filesystems. This is the
: dirpref changes biting you. Warner, we probably need an entry in UPDATING for
: the dirpref changes that warn people to build and install a new fsck before
: boo
In message <[EMAIL PROTECTED]> Mike Smith writes:
: I assume there's a better fix in the works, so that a "dirpref-touched"
: disk can be moved back to a pre-dirpref system?
If not, then dirpref should be backed out, imho.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
In message <03cb01c0cb0b$ce9369a0$[EMAIL PROTECTED]> "Chris Knight" writes:
: I've found the following sequence to be optimal from going from
: pre-dirpref -current to post-dirpref -current and 4-stable to -current:
But that won't work going from a pre-dirpref -stable to a post-dirpref
-currnet b
The last set of changes to fsck_ffs moved the initialisation of
dev_bsize to sblock_init(), but this is not called by fsdb(8) so
fsdb dies almost immediately with a floating exception. I'm just
going to commit the obvious fix, which is to have fsdb call
sblock_init() also.
Ian
To Unsubscribe: s
hello, world\n
my current kernel cvsupped around Apr 14th tells me about
duplicate locks and lock order reversal. Is this reason to worry?
...
Apr 23 22:23:09 hal9000 /boot/kernel/kernel: da0 at ahc0 bus 0 target 2 lun 0
Apr 23 22:23:10 hal9000 /boot/kernel/kernel: da0: Fixed Direct
Access SCSI
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : I assume there's a better fix in the works, so that a "dirpref-touched"
> : disk can be moved back to a pre-dirpref system?
>
> If not, then dirpref should be backed out, imho.
I'd have to agree; this was a pretty poorly-thought-out aspect
On Mon, 23 Apr 2001, Mart Norman wrote:
> Hi!
>
> I'm trying to upgrade from 3.0 to 4.3 but make buildworld fails
>
> cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused
> -Wmissing-prototypes -Wredundant-decls
> -I/usr/obj/usr/src/i386/usr/include -static -o config config.o main.o
> la
To: Kirk McKusick <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: fsdb broken in -current
Date: Mon, 23 Apr 2001 22:23:48 +0100
From: Ian Dowse <[EMAIL PROTECTED]>
The last set of changes to fsck_ffs moved the initialisation of
dev_bsize
On 23-Apr-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
>: You need to rebuild fsck and install it and fsck your filesystems. This is
>: the
>: dirpref changes biting you. Warner, we probably need an entry in UPDATING
>: for
>: the dirpref changes that warn people
In message <[EMAIL PROTECTED]> John Baldwin writes:
:
: On 23-Apr-01 Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> John Baldwin writes:
: >: You need to rebuild fsck and install it and fsck your filesystems. This is
: >: the
: >: dirpref changes biting you. Warner, we probably need an e
On 23-Apr-01 Jens Schweikhardt wrote:
> hello, world\n
>
> my current kernel cvsupped around Apr 14th tells me about
> duplicate locks and lock order reversal. Is this reason to worry?
> ...
> Apr 23 22:23:09 hal9000 /boot/kernel/kernel: da0 at ahc0 bus 0 target 2 lun 0
> Apr 23 22:23:10 hal9000
On 23-Apr-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
>:
>: On 23-Apr-01 Warner Losh wrote:
>: > In message <[EMAIL PROTECTED]> John Baldwin writes:
>: >: You need to rebuild fsck and install it and fsck your filesystems. This
>: >: is
>: >: the
>: >: dirpref cha
In message <[EMAIL PROTECTED]> John Baldwin writes:
: Yes, but until such time as we do that we should warn people in UPDATING at
: least.
20010411:
fsck and the kernel were changed to handle some optimizations
to directory layout. This breaks backward compatbility.
Updat
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>:
>: Yes, but until such time as we do that we should warn people in UPDATING at
>: least.
>:
>
>OK, but you won't like the UPDATING entry.
The bug actually looks fairly simple to fix. ffs_reload() isn't
checking if the new superblock fields
In message <[EMAIL PROTECTED]> John Baldwin writes:
: I didn't do dirpref and I want to see this fixed as well. :( I just want to
: give people a fighting chance of making it past this change.
Ah. Sorry for directing my grumpiness about the quality of the change
against you.
Warner
To Unsubsc
Bruce Evans wrote:
> On Mon, 23 Apr 2001, Mart Norman wrote:
>
> > Hi!
> >
> > I'm trying to upgrade from 3.0 to 4.3 but make buildworld fails
> >
> > cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused
> > -Wmissing-prototypes -Wredundant-decls
> > -I/usr/obj/usr/src/i386/usr/include -
On 23-Apr-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
>: Yes, but until such time as we do that we should warn people in UPDATING at
>: least.
>
> 20010411:
> fsck and the kernel were changed to handle some optimizations
> to directory layout. This br
Hello Kris,
Monday, April 23, 2001, 2:50:48 AM, you wrote:
>> 'make buildworld' fails with the following symptoms:
>> ===> usr.sbin/rpc.lockd
[skipped]
>> Stop in /garbage/src/usr.sbin/rpc.lockd.
>> *** Error code 1
KK> Looks like you're building with -j,
no, i read about potential problems
On 23-Apr-01 Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Warner Losh
> writes:
>>:
>>: Yes, but until such time as we do that we should warn people in UPDATING at
>>: least.
>>:
>>
>>OK, but you won't like the UPDATING entry.
>
> The bug actually looks fairly simple to fix. ffs_reload()
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>
>
>Fair enough, I guess ffs_reload() should just sanity check the values. Any
>takers?
You could try this (untested). I have to run now, but I can test it
later as it's easy enough to reproduce.
Ian
Index: ffs_vfsops.c
> Rodney W. Grimes <[EMAIL PROTECTED]> wrote:
> > > Before anyone starts writing scripts, consider that {} will be
> > > replaced by xargs with (roughly) ARG_MAX - 10 characters worth of the
> > > stuff coming off the pipe. If your combined arguments plus
> > > environment exceeds ARG_MAX
In message <[EMAIL PROTECTED]>, Ian Dowse writes:
>You could try this (untested). I have to run now, but I can test it
>later as it's easy enough to reproduce.
Almost, but I missed the fs_contigdirs field, which was the real
culprit. An updated patch is below; this seems to stop the panics
for me
On Mon, 23 Apr 2001, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, John Baldwin writes:
> >
> >
> >Fair enough, I guess ffs_reload() should just sanity check the values. Any
> >takers?
>
> You could try this (untested). I have to run now, but I can test it
> later as it's easy enough to re
Hello, How can I increase free vnodes? kernel very often falls with message
'no free vnode'.
Right now after reboot numbers of vnodes are:
9913 desiredvnodes
556 numvnodes
25 freevnodes
--
bye
Juriy Goloveshkin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubsc
You can find the work I've done so far to make a giant vm mutex
here:
http://people.freebsd.org/~alfred/vm.diff
It doesn't work (of course :)) it dies really early in the
intialization when a vm_page is manipulated without the lock. It
dies before it even gets to calibrating the clocks. I've b
On Mon, 23 Apr 2001, Alfred Perlstein wrote:
> requires vm_page_queues_mtx:
> manipulation of vm_page_queues
[snip]
> pmaps spotted:
> pmap_copy_page
> pmap_page_protect
There is potential for nasty lock ordering conflicts here.
Page faults will govm_mtx -> vm_page_queues_mtx
The pageout
[please CC replies; I'm not on the -current list]
I'm trying to boot a -CURRENT kernel to confirm it really does fix a problem
with my hardware (see kern/26046).
I've tried a couple of snapshots from current.freeebsd.org between 1st the 15th
April. None has booted. Each dies with an integer d
On Mon, 23 Apr 2001, Peter Wemm wrote:
> Bruce Evans wrote:
> > On Mon, 23 Apr 2001, Mart Norman wrote:
> > > Any hints what should i do to make buildworld successful?
> >
> > Start by deleting usr.sbin/config from bootstrap-tools. You won't be
> > able to build any kernels until the new world
39 matches
Mail list logo
