In message <[EMAIL PROTECTED]>, John Hay write
s:
>>
>> But while you're at it, migrate to md(4) instead of vn(4), it does
>> vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
>>
>
>So why not change the release process to use md instead of vn, so that
>we can make sure it
In message <[EMAIL PROTECTED]> John Baldwin writes:
: 2) It hides the output from config(8). config(8) prints out all sorts of
: useful warnings when options are deprecated, etc., but buildkernel hides these
: from the user. The problem is that config(8) is by design an interactive tool,
: which
On Sun, Jan 21, 2001 at 11:35:49PM -0800, John Baldwin wrote:
>
> On 22-Jan-01 Donald J . Maddox wrote:
> >
> > 1) rm -r /usr/include; cd /usr/src; make includes
>
> I just do 'make includes' w/o the rm of /usr/include when I do this..
I used to do 'make -DCLOBBER includes' to make sure no old
Manual page of rtprio(1) says it returns exit value 0 on success when
PID is specified via argument. But current rtprio(1) returns 1
whether rtprio(2) is processed successfully or not.
This patch seems to fix to return 0 on success as documented in
manpage.
Please let me know if it is wrong...
In message <[EMAIL PROTECTED]> "Donald J . Maddox" writes:
: way of doing things now. It appears that these pronouncements were
: premature at best.
Actually no. It isn't premature. It is the canonical way. It is how
we've been telling people to build it for at least the past year or
so. Som
>
> But while you're at it, migrate to md(4) instead of vn(4), it does
> vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
>
So why not change the release process to use md instead of vn, so that
we can make sure it works before vn is axed?
John
--
John Hay -- [EMAIL PR
On 22-Jan-01 Donald J . Maddox wrote:
> Ok, fair enough. I have to confess that my usual procedure remains,
> as it has been for a long time, like this:
>
> 1) rm -r /usr/include; cd /usr/src; make includes
I just do 'make includes' w/o the rm of /usr/include when I do this..
I normally do t
On 22-Jan-01 The Hermit Hacker wrote:
> On Sun, 21 Jan 2001, Peter Wemm wrote:
>
>> The Hermit Hacker wrote:
>> >
>> > d'oh, did it backwards again ... buildkernel then buildworld ... let me go
>> > back and rebuild kernel and see if that is all it was in my case ...
>>
>> Argh! I wish people wo
Ok, fair enough. I have to confess that my usual procedure remains,
as it has been for a long time, like this:
1) rm -r /usr/include; cd /usr/src; make includes
This may be controversial, but it has always worked for me, and although
it's not supposed to (in my understanding), the build (I thin
In message <[EMAIL PROTECTED]>, Thierry Herbelot writes:
>Poul-Henning Kamp wrote:
>>
>> But while you're at it, migrate to md(4) instead of vn(4), it does
>> vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
>
>If I may, two more questions :
Sorry, my misundertstanding, s
Poul-Henning Kamp wrote:
>
> But while you're at it, migrate to md(4) instead of vn(4), it does
> vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
If I may, two more questions :
- the 4.2 man page for vn says the file must be stored locally (I have
tried vn-mounting a NF
On 22-Jan-01 John Baldwin wrote:
>
> On 22-Jan-01 Donald J . Maddox wrote:
>> On Sun, Jan 21, 2001 at 10:49:30PM -0800, Peter Wemm wrote:
>>>
>>> Argh! I wish people would stop using buildkernel! :-( It calls config(8)
>>> in such a way that buries the warning messages where people dont see.
>
On Sun, 21 Jan 2001, Peter Wemm wrote:
> The Hermit Hacker wrote:
> >
> > d'oh, did it backwards again ... buildkernel then buildworld ... let me go
> > back and rebuild kernel and see if that is all it was in my case ...
>
> Argh! I wish people would stop using buildkernel! :-( It calls config(
On 22-Jan-01 Donald J . Maddox wrote:
> On Sun, Jan 21, 2001 at 10:49:30PM -0800, Peter Wemm wrote:
>>
>> Argh! I wish people would stop using buildkernel! :-( It calls config(8)
>> in such a way that buries the warning messages where people dont see.
>> config(8) is meant to be used interactiv
-On [20010120 08:40], Alex Kapranoff ([EMAIL PROTECTED]) wrote:
>Additional symptoms include very high system CPU state percentage and
>a lot of page faults.
A page fault is not a bad thing, it is merely an indicator from the CPU
to the kernel that the page you want to refer to, the next page of
-On [20010121 23:10], Salvo Bartolotta ([EMAIL PROTECTED]) wrote:
>Following Warner's directions in internat.txt, I removed the
>crypto-related stuff, and issued the following explicit command:
One question: why?
crypto is now folded into src-all
--
Jeroen Ruigrok van der Werven
-On [20010122 07:55], Peter Wemm ([EMAIL PROTECTED]) wrote:
>The Hermit Hacker wrote:
>>
>> d'oh, did it backwards again ... buildkernel then buildworld ... let me go
>> back and rebuild kernel and see if that is all it was in my case ...
>
>Argh! I wish people would stop using buildkernel! :-(
On Sun, Jan 21, 2001 at 10:49:30PM -0800, Peter Wemm wrote:
>
> Argh! I wish people would stop using buildkernel! :-( It calls config(8)
> in such a way that buries the warning messages where people dont see.
> config(8) is meant to be used interactively :-(
Is there another target that will ge
The Hermit Hacker wrote:
>
> d'oh, did it backwards again ... buildkernel then buildworld ... let me go
> back and rebuild kernel and see if that is all it was in my case ...
Argh! I wish people would stop using buildkernel! :-( It calls config(8)
in such a way that buries the warning messages
On 22-Jan-01 Jun Kuriyama wrote:
>
> After installworld'ing today, I cannot compile emulators/vmware2.
> Does someone see this result?
Fix it to #include instead ofwas
just recently gutted and/or axed (can't remember which). If doesn't
work on stable, just do a #ifdef __FreeBSD_version >
But while you're at it, migrate to md(4) instead of vn(4), it does
vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
Poul-Henning
In message <[EMAIL PROTECTED]>, Thierry Herbelot writes:
>thanks a lot : that was it !
>
>Peter Jeremy wrote:
>>
>> On 2001-Jan-21 10:15:22
thanks a lot : that was it !
Peter Jeremy wrote:
>
> On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot <[EMAIL PROTECTED]> wrote:
> >I've got a recent current (cvsuped and rebuilt yesterday) on a laptop
> >and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel
> >and I've also tr
After installworld'ing today, I cannot compile emulators/vmware2.
Does someone see this result?
-
cc -O -mpentiumpro -pipe
-I/tmp/work/home/ports/emulators/vmware2/work/vmware-distrib/vmmon-only/include
-I/tmp/work/home/ports/emulators/vmware2/work/vmware-distrib/vmmon-only/common
-I/tmp
d'oh, did it backwards again ... buildkernel then buildworld ... let me go
back and rebuild kernel and see if that is all it was in my case ...
On Sun, 21 Jan 2001, Peter Wemm wrote:
> The Hermit Hacker wrote:
> >
> > just tried to reboot with a latest build (from this afternoon), and upon
> >
The Hermit Hacker wrote:
>
> just tried to reboot with a latest build (from this afternoon), and upon
> reboot, it gives:
>
> pid 6 (sh), uid 0: exited with signal 8
>
> when /etc/rc tries to run, and, of course, won't let me get to single user
> mode for same reason ...
>
> checked /usr/src/U
On Sun, Jan 21, 2001 at 03:29:22PM -0800, Kris Kennaway wrote:
> On Sun, Jan 21, 2001 at 06:05:20AM -0500, Donald J . Maddox wrote:
>
> > It may have absolutely nothing to do with either of these cases, but
> > I found out the hard way recently that booting with no device.hints
> > in /boot will
just tried to reboot with a latest build (from this afternoon), and upon
reboot, it gives:
pid 6 (sh), uid 0: exited with signal 8
when /etc/rc tries to run, and, of course, won't let me get to single user
mode for same reason ...
checked /usr/src/UPDATING, and nothing in there seems to apply
On Sun, Jan 21, 2001 at 06:05:20AM -0500, Donald J . Maddox wrote:
> It may have absolutely nothing to do with either of these cases, but
> I found out the hard way recently that booting with no device.hints
> in /boot will exhibit symptoms that appear identical to this. Is it
> possible that so
>> Original Message <<
On 1/21/01, 11:28:46 PM, Szilveszter Adam
<[EMAIL PROTECTED]>
wrote regarding Re: cvsup'ing repo & cvs-checkout'ing sources makes
cvs
complain...:
> Dear Salvo,
> So if you want to place a directory under CVS control, you must
> first rm -
Dear Salvo,
Maybe I do not know your problem exactly but I am trying to find out...
I think that what you saw at first try was related to the fact that the
source tree you tried to upgrade did not have CVS directories in each
directory. These directories are needed for proper CVS operation. If y
On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot <[EMAIL PROTECTED]> wrote:
>I've got a recent current (cvsuped and rebuilt yesterday) on a laptop
>and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel
>and I've also tried to kldload vn.ko, but I get consistently "vn0c :
>device
/* apologies if this is not the most appropriate list; [additional]
* apologies for the long post; suggestions and pointers gladly
* accepted.
*/
Dear FreeBSD'ers,
Over the past few days, I have been cvsup'ing FreeBSD's repository
and cvs-checkout'ing out my -CURRENT sources; for the record,
On Sun, Jan 21, 2001 at 01:06:15PM -0500, Bosko Milekic wrote:
>
> > http://people.freebsd.org/~jasone/diffs/mutex_f_3.diff
>
> This looks like a variation of Peter's mutex.diff which moves a bunch of
> macros to kern/kern_mutex.c from sys/mutex.h - so is it final now that we
> will move the
In message <[EMAIL PROTECTED]> Jason Evans writes:
: Several of us have started experiencing problems with kernels that won't
: boot. The symptom is hard to miss: the machine locks up at the spinner
: just before printing the copyright message at the beginning of the boot
: sequence.
I've seen t
:
:The loopback nfs hangs that have been with us for a month have now propagated
:to -stable.
Can you break into DDB and get a 'ps' and a kernel core? There are a
bunch of things it could be, including possibly my low-memory deadlock
code (which concentrated more on UFS and not so mu
Kris Kennaway wrote:
>
> On Sun, Jan 21, 2001 at 01:51:05AM -0600, David Syphers wrote:
>
> > the binaries from a directory labeled "FreeBSD 5.x". So I tried the ports,
> > and it built fine for a long time, and then after about 35300 lines of
> > output to the screen, ran into
> >
> > make: do
Guys, I've noticed that some of you have been making noises about
cleaning up the NFS macros in current.
I strongly recommend that you not do this, at least not unless
you want to take on a man month (or two!) worth of work & debugging!
In fact, I would recommend that the NFS
The loopback nfs hangs that have been with us for a month have now propagated
to -stable.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Jason Evans wrote:
> Peter Wemm noticed that WITNESS currently causes a kernel trap the alpha.
> The bug also exists on x86, but does not necessarily cause any problems.
> If you run into problems (probably during boot), there is a patch available
> that should fix the WITNESS problem:
>
> http:
Hello.
After resup few hours ago, i try to buildworld on
FreeBSD 5.0-CURRENT #0: Sat Jan 13 22:57:43 MSK 2001
gzip -cn /usr/src/lib/libc/../libc/regex/re_format.7 > re_format.7.gz
make in free(): error: junk pointer, too high to make sense.
Abort trap - core dumped
*** Error code 134
Stop in /us
On Sun, 21 Jan 2001, Will Andrews wrote:
> The timespec* stuff is hidden behind the _KERNEL aura on FreeBSD, but
> not on OpenBSD. This is manifested in OpenBSD's make source, which uses
> timespec for a few things.
>
> So now, maybe someone can answer my question: why is timespec _KERNEL?
The
Huh, I removed '-O' switch from ${CFLAGS} and managed to rebuild
and reinstall gcc. This new (in fact the same) gcc now works fine both
with '-O' and without it. Looks like a pilot error. Strange, anyway.
Sorry to bother you all.
On Sun, Jan 21, 2001 at 02:50:48PM +0300, Alex Kapranoff wrote:
> I
Peter Wemm noticed that WITNESS currently causes a kernel trap the alpha.
The bug also exists on x86, but does not necessarily cause any problems.
If you run into problems (probably during boot), there is a patch available
that should fix the WITNESS problem:
http://people.freebsd.org/~jasone/dif
My -CURRENT SMP box (Digital Prioris 5166HX running friday's -CURRENT
unmodified) refuses to dump core. If I type 'panic' at the DDB prompt
after a trap (I've had different types - mainly page faults in vinum
and lock order violation in the SIGINFO handler in tty.c), it goes
into recursive panic (
Hello!
After cvsuped, i try to build world under FreeBSD 5.0-CURRENT #0: Sat Jan 13 22:57:43
MSK 2001
===> usr.bin/kdump
cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace
-I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/u
sr/include -c /usr/src/usr.bin/kdump/kdump.c
cc -O -
I have -CURRENT on a UP P166 box.
I've just managed to build a new kernel and world (cvsuped yesterday)
and installed them both. Now I get:
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1
Stop in /usr/home/alex/work/own.
whenever I want to compile something not so
On Sun, Jan 21, 2001 at 02:32:38AM -0800, Jason Evans wrote:
> We don't know why this is happening, and at this point the primary
> suspicion is that this problem has been lurking for quite some time, and
> we've recently committed a combination of changes that causes the problem
> to exhibit itse
> the hostname, one being a syscall and the other being a sysctl. One
> could of course have the kernel print a message to the console about
> it, syslogd(8) would pick that up.
Yes, I was about to propose this, but then I thought: why? If we go this way,
then we should definitely also log an IP
On Sun, Jan 21, 2001 at 02:32:38AM -0800, Jason Evans wrote:
> Several of us have started experiencing problems with kernels that won't
> boot. The symptom is hard to miss: the machine locks up at the spinner
> just before printing the copyright message at the beginning of the boot
> sequence.
On Sun, Jan 21, 2001 at 01:51:05AM -0600, David Syphers wrote:
> the binaries from a directory labeled "FreeBSD 5.x". So I tried the ports,
> and it built fine for a long time, and then after about 35300 lines of
> output to the screen, ran into
>
> make: don't know how to make ../../../fonts
Hello,
I've got a recent current (cvsuped and rebuilt yesterday) on a laptop
and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel
and I've also tried to kldload vn.ko, but I get consistently "vn0c :
device not configured" when I try to use it to mount a locally stored
iso imag
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>
>On 20-Jan-01 Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, John Baldwin writes:
>>>
>>>On 20-Jan-01 The Hermit Hacker wrote:
On Sat, 20 Jan 2001, Mark Murray wrote:
> >
> > on a 2xPII/350, 256M, two scsi disks
52 matches
Mail list logo
