On Tue, Oct 05, 1999 at 08:33:54AM +0200, Mark Murray <[EMAIL PROTECTED]> wrote:
> > I've seen a few reports that CVSup has suddenly started dumping
> > core on a segmentation violation under -current, but I need more
> > information. For starters, I would like to know whether the static
> > bin
> I've seen a few reports that CVSup has suddenly started dumping
> core on a segmentation violation under -current, but I need more
> information. For starters, I would like to know whether the static
> binary (ports/net/cvsup-bin) works or not under the very latest
> -current on the i386. Coul
> > > 3: *always* build (or try to) and install a new kernel before a
> > >make world as that's a lot easier to back out of.
> >
> > This badly bites the bum of anyone who uses KLD's regularly.
>
> 4: Don't use modules in -current unless you know what you are doing.
> This normally means not
My machine is dual boot and I don't have time to reboot now. (I need to get
some sleep.) I'll provide what information I can quickly and will test things
further tomorrow evening.
I was seeing the core dumps from gui cvsup. My current was a couple different
cvsup runs on Saturday and Sunday.
On Mon, 4 Oct 1999, Timo Geusch wrote:
> If you're interested I can send you the source code for the driver but it is
> not clear if it works on -current at the moment as I haven't updated for
> some time.
Send it here as I'm working on if_ep in some fashion.
Someone find me a verified PnP 3c509
On Fri, Oct 01, 1999 at 03:36:11PM -0400, Daniel Eischen wrote:
> But this still doesn't entirely solve the problem. You still have
> to build and install a new kernel before installing the world.
Of course! Installing the world _is_ upgrading your operating
system. I don't see anyone suggesti
I've seen a few reports that CVSup has suddenly started dumping
core on a segmentation violation under -current, but I need more
information. For starters, I would like to know whether the static
binary (ports/net/cvsup-bin) works or not under the very latest
-current on the i386. Could somebody
In article <[EMAIL PROTECTED]>,
Chad R. Larson <[EMAIL PROTECTED]> wrote:
>
> John, do you have usage statistics broken out for each server?
I don't, but I wish I did. It would be an interesting project for
somebody to write tools that could analyze the cvsupd log files to get
information like
Mark Newton wrote:
> A similar box which I rebooted (for an upgrade from 2.2.5 to 3.2) about
> a fortnight ago:
>
> 3:38PM up 471 days, 5:59, 1 user, load averages: 0.00, 0.02, 0.00
>
> ... and, before this thread gets completely out of control, I direct
> posters to http://uptime.viper.net.
Mark Murray wrote:
> > 7:46PM up 375 days, 20:09, 2 users, load averages: 0.00, 0.01, 0.00
> > FreeBSD xx.xxx.xxx 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Tue May 5
>15:51:34 SAST 1998 [EMAIL PROTECTED]:/usr/src/sys/compile/XXX i38
> 6
>
> This box was used as a shell server
> > 3: *always* build (or try to) and install a new kernel before a
> >make world as that's a lot easier to back out of.
>
> This badly bites the bum of anyone who uses KLD's regularly.
4: Don't use modules in -current unless you know what you are doing.
This normally means not using modules
Hi Guido,
> I have a 3.3.-stable system and somehow I cannot make buildworld
> a current tree.
> The porblem is:
> cc -c -I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config
>-I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC
>-I/usr/obj/alt/usr/src/tmp
replying to my own message but I think I found a solution...
It seems that something was stale in /usr/include, I was able to
fix the problem by:
rm -rf /usr/include/*
cd /usr/src
make includes
cd /usr/src/lib/libc_r
make
make install
funny part is that two successive make worlds didn't seem
Hi,
I have a 3.3.-stable system and somehow I cannot make buildworld
a current tree.
The porblem is:
cc -c -I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config
-I/alt/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC
-I/usr/obj/alt/usr/src/tmp/usr/include -DL
Hi,
I just committed the sigcontext changes. sigreturn can now again be
called with an argument of type sigcontext but also with an argument of
type ucontext_t. Also, signal handlers can define their third argument
to be both of type struct sigcontext* and ucontext_t*. This should fix
the source
Chuck Robey wrote:
>
> I just tried to use my copy of WordPerfect 8 to decode an rtf document,
> like I've done before the signal change, and boy was I surprised. The
> machine locked up for 10 seconds, then spontaneously rebooted.
>
> Anyone else have this experience with Linux emulation?
Som
On Thu, 30 Sep 1999, Juan Amado Becerril Castillo wrote:
> Suggestions ???
Not mail the list 3 f'ing times, to start.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] -
To Unsubscribe: send mail to [EM
I am running FreeBSD 4.0. I have been seeing the empty core files from
netscape 4.61 and (as of last night) 4.7 for at least a week. I use
fvwm2 and afterstep-devel. The behavior seems to be independant of the
window manager. I rebuilt all my ports (including X and new X aout
files) with the new
: Excuse my intrusion, but could you be so kind to tell me whether you had
:the time to build patches for these MMAP-related freezes ? If not could
:you recommend me some workarounds ?
:
: I have a -stable production server that keeps (solidly) blocking pretty
:often (I don't get over 3 days uptim
I just tried to use my copy of WordPerfect 8 to decode an rtf document,
like I've done before the signal change, and boy was I surprised. The
machine locked up for 10 seconds, then spontaneously rebooted.
Anyone else have this experience with Linux emulation?
--
Mark Murray wrote:
> > 3: *always* build (or try to) and install a new kernel before a
> >make world as that's a lot easier to back out of.
>
> This badly bites the bum of anyone who uses KLD's regularly.
>
> I suspect that _now_ is the time to try to make thes build at
> kernel build time,
Andre,
I had the same problem with my laptop and what worked for me was to boot
it in single user with my old kernel, fsck all disk partitions, mount
all partitions -w including root with -u -w, make a new kernel, reboot
again in single user and remount everything and make world. I was then
ok,
Juan Amado Becerril Castillo wrote:
>
> Suggestions ???
Sure. Read the mailing list you are posting to.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Rule 69: Do unto other's code as you'd have it done unto yours
To Unsubscribe: send mail to
On Mon, 4 Oct 1999, Adrian Penisoara wrote:
>
> Excuse my intrusion, but could you be so kind to tell me whether you had
> the time to build patches for these MMAP-related freezes ? If not could
> you recommend me some workarounds ?
doubling the ram from 384 -> 768 meg appears to have fixed it
> 7:46PM up 375 days, 20:09, 2 users, load averages: 0.00, 0.01, 0.00
> FreeBSD xx.xxx.xxx 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Tue May 5 15:51:34
>SAST 1998 [EMAIL PROTECTED]:/usr/src/sys/compile/XXX i38
6
This box was used as a shell server for more than a year; it was
hardene
> 3: *always* build (or try to) and install a new kernel before a
>make world as that's a lot easier to back out of.
This badly bites the bum of anyone who uses KLD's regularly.
I suspect that _now_ is the time to try to make thes build at
kernel build time, and also move to some subdirector
And *don't* post the same thing three times to the lists unless you want
to find yourself filtered out!
Juan Amado Becerril Castillo wrote:
> Suggestions ???
>
> --
> >>> elf make world started on Thu Sep 30 09:23:09 CDT 1999
>
Juan Amado Becerril Castillo wrote:
> Suggestions ???
1: Read freebsd-current and it would have told you!
2: Build a new kernel first before 'make world'.
3: *always* build (or try to) and install a new kernel before a
make world as that's a lot easier to back out of.
[..]
> echo '#include "i
On Mon, 4 Oct 1999, Marcel Moolenaar wrote:
> Alfred Perlstein wrote:
> >
> > Since the signal changes...
> >
> > I'm finding that it _seems_ since libc_r isn't including something
> > that properly defines __inline to inline that i'm getting unresolved
> > symbols when linking or running prog
Hi,
On Mon, 14 Jun 1999, Matthew Dillon wrote:
>
> :>
> :> David, can you email this program to me please?
> :>
> :> Also, which FreeBSD release does this occur on?
> :>
> :> I've got about 6 mmap-related bugs on my plate at the moment. 3 of them
> :> have been identified (
You need to move your sources further forward.
In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes:
>A kernel from this weekend's sources is showing this warning message
>at boot:
>
>WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0
>??
>
>These are:
>
>brw-r- 1 root
A kernel from this weekend's sources is showing this warning message
at boot:
WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0
??
These are:
brw-r- 1 root operator 30, 0x00030004 Apr 6 11:48 ad0s2e
brw-r- 1 root operator 30, 0x00030005 Apr 6 11:48 ad0s2f
I
Anybody can help me, how I can fix this !
Thanks.
===> c++filt
/usr/obj/usr/src/gnu/usr.bin/cc/c++filt created for
/usr/src/gnu/usr.bin/cc/c++filt
===> doc
/usr/obj/usr/src/gnu/usr.bin/cc/doc created for
/usr/src/gnu/usr.bin/cc/doc
===> f77
/usr/obj/usr/src/gnu/usr.bin/cc/f77 created for
/usr/
Suggestions ???
--
>>> elf make world started on Thu Sep 30 09:23:09 CDT 1999
--
--
>>> Cleaning up the temporary el
Suggestions ???
--
>>> elf make world started on Thu Sep 30 09:23:09 CDT 1999
--
--
>>> Cleaning up the temporary el
WARNING: the following reply contains Extreme Ranting which may be too
intense for young audiences. Those not wishing to experience Extreme
Ranting should #define NO_EXTREME_RANTING.
Of all the gin joints in all the towns in all the world, Bryan Bursey
had to walk into mine and say:
> I attemp
Anyone in the current folks know why I might be getting problems with
FreeBSD on an Adaptec 1540 controller?
The machine works fine on 2.2.8 and 2.2.6, but dies a horrible screeching
halt when installing 3.3 or 4.0. It literally just locks up solid when
3.3 or 4.0 probes the machine during the
Greg,
thanks for your help, no i didn't get the heads up because i just got
onto the current list, but i should get them now if any occur. I'll try
building current again
Thanks
Bill
[EMAIL PROTECTED]
- Original Message -
From: Greg Lehey <[EMAIL PROTECTED]>
To: Bill A. K. <[EMAIL
While testing the new swopen() routine I found this panic(8)
implementation on -current:
hexdump -C < /dev/drum
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time befor
And the crowd goes wild!
Nick
>
> We have now come so far that we can start to kill cdevsw_add()
> calls and rely on make_dev() for most of the device drivers.
>
> Later today I will add a "nagging printf", which will trigger when
> a device is opened, which wasn't registered by the dev
Hello
It looks like I fucked my -current box up during the sig_t changes.
I tried made a new kernel before make world but after ifconfig'ing
the network interfaces it panics with:
panic: malloc type lacks magic
Making a new world is of course not possible because of the sig_t
changes.
Any ide
It seems Timo Geusch wrote:
> On Fri, Oct 01, 1999 at 02:32:11PM +0200, Soren Schmidt wrote:
> > Hmm, I also have severe problems with the PnP stuff and my 3C509
> > cards, it just wont work as the pnp code finds and allocates
> > adresses for the card, but the card probe doesn't pick them up...
>
In message <[EMAIL PROTECTED]>, Darren Reed writes
:
>In some email I received from Poul-Henning Kamp, sie wrote:
>>
>>
>> We have now come so far that we can start to kill cdevsw_add()
>> calls and rely on make_dev() for most of the device drivers.
>[...]
>
>Is that make_dev() meant to make mak
In some email I received from Poul-Henning Kamp, sie wrote:
>
>
> We have now come so far that we can start to kill cdevsw_add()
> calls and rely on make_dev() for most of the device drivers.
[...]
Is that make_dev() meant to make makedev() or is that a part of the
transition you're helping alo
On Fri, Oct 01, 1999 at 02:32:11PM +0200, Soren Schmidt wrote:
> Hmm, I also have severe problems with the PnP stuff and my 3C509
> cards, it just wont work as the pnp code finds and allocates
> adresses for the card, but the card probe doesn't pick them up...
Soren,
AFAIK the ep driver does not
We have now come so far that we can start to kill cdevsw_add()
calls and rely on make_dev() for most of the device drivers.
Later today I will add a "nagging printf", which will trigger when
a device is opened, which wasn't registered by the device driver
with make_dev(). It will only trigger o
On Sun, 03 Oct 1999 08:09:49 -0300, Bryan Bursey wrote:
> Can anyone tell me if there are known issues with the xl0 driver in 4.0,
> or if it has been superceded by another driver which works with 3Com
> 3C900B.
That's a pretty broad question. I know that lots of people use the xl0
driver in C
On Sun, 3 Oct 1999, Daniel Eischen wrote:
> Doug Rabson wrote:
> > I looked at you pnpinfo again and I think this change might be better. It
> > accepts the cards description instead of overriding it and adds another ID
> > for SUP2080 which your card is compatible with. I also removed the bogus
Alfred Perlstein wrote:
>
> Since the signal changes...
>
> I'm finding that it _seems_ since libc_r isn't including something
> that properly defines __inline to inline that i'm getting unresolved
> symbols when linking or running programs that depend on libc_r.
>
> Anyone else getting this?
>
49 matches
Mail list logo
