Re: HEADS UP: sigset_t changes committed

I know this is not topic related, so appologies in advance ... Sometimes people deserve a pat on the back. This is the best thing since Chocolate Chip cookies :) We're running things like myth2_demo, and it opens the doors to a whole bunch of applications ... e.g. C++ Builder to follow next ye

Re: HEADS UP: sigset_t changes committed

Amancio Hasty scribbled this message on Sep 30: > BTW: I think that what you are doing is really great !! > > Hmm... I wonder if the volume in the list will increase with cool > apps such as IBM's ViaVoice which needs your mods to work. I happen to agree that this is a good move for FreeBSD, bu

Re: HEADS UP: sigset_t changes committed

Marcel Moolenaar scribbled this message on Sep 30: > [cc list trimmed] > > John-Mark Gurney wrote: > > > actually, no, I would like this fixed... I will be unable to develope > > FreeBSD if the tools target doesn't work!! I do all of my compiles on > > a 3.0-R box (yes, that's right, 3.0-R) and

Re: HEADS UP: sigset_t changes committed

[cc list trimmed] John-Mark Gurney wrote: > actually, no, I would like this fixed... I will be unable to develope > FreeBSD if the tools target doesn't work!! I do all of my compiles on > a 3.0-R box (yes, that's right, 3.0-R) and it will basicly stop me from > doing any of that... I'm not sure

Re: how to avoid bullets in the feet (was Re: HEADS UP: sigset_t changescommitted)

Alfred Perlstein wrote: > > What's really needed is some warning sort of like what we > did when the AOUT->ELF convertion happened, there has > to be a simple way to test this as part of installworld. Yes, that's exactly what I had in mind. Details still need to be worked out, though. -- Marce

Re: HEADS UP: sigset_t changes committed

John Polstra wrote: > > I got world built and installed OK on the alpha now, and things > generally seem OK. However, amd dumped core with a SEGV immediately > upon startup. I haven't had even a second to try to debug it yet. > Just thought I'd let you know about it. ...and there was much rejo

Re: HEADS UP: sigset_t changes committed

BTW: I think that what you are doing is really great !! Hmm... I wonder if the volume in the list will increase with cool apps such as IBM's ViaVoice which needs your mods to work. Tnks ! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "u

Re: HEADS UP: sigset_t changes committed

Harold Gutch wrote: > > I interpreted the way of currently handling things (build the > kernel first, then the userland) to be a _temporary_ solution, > that Marcel was working on being fixed. If this is not the case, > then I agree with you. I'm not working on changing the build/installworld. T

Re: HEADS UP: sigset_t changes committed

Hi, On Wed, Sep 29, 1999 at 10:07:07PM -0700, John-Mark Gurney wrote: > Garrett Wollman scribbled this message on Sep 29: > > <<[EMAIL PROTECTED]> said: > > > > > If it is broken, please back out the signal changes or fix the tools > > > target. > > > > No, Rod, just Deal With It(tm). > > actu

Re: HEADS UP: sigset_t changes committed

Garrett Wollman scribbled this message on Sep 29: > <<[EMAIL PROTECTED]> said: > > > If it is broken, please back out the signal changes or fix the tools > > target. > > No, Rod, just Deal With It(tm). actually, no, I would like this fixed... I will be unable to develope FreeBSD if the tools ta

Re: HEADS UP: sigset_t changes committed

In message <[EMAIL PROTECTED]> Peter Jeremy writes: : I think that a suitable upgrade procedure should have been thought : through and implemented before the changes were committed. It would : also have been nice to have a CVS tag. It's a bit late now though. It is never too late to lay down a

Re: HEADS UP: sigset_t changes committed

On Thu, Sep 30, 1999 at 02:37:45PM +1000, Warner Losh wrote: >In keeping notes, what would need to happen would be that you'd have >to build config as well as all the tools to build binaries. We might be able to get away with temporarily replacing the i386/include/atomic.h[1] with the one from -s

Re: HEADS UP: sigset_t changes committed

Would it at least be possible to add a test to the make-world makefile, saying "if kernel_version < xyzzy then echo 'Sorry, install new kernel first' exit 9 fi" Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: sigset_t changes committed

In message <[EMAIL PROTECTED]> Peter Jeremy writes: : We've never required this before. I managed to convert from 2.2.6 to : -current using `make upgrade'. Why should I need to FTP a kernel : from another machine to go from 3.x to 4.x? In keeping notes, what would need to happen would be that y

Re: HEADS UP: sigset_t changes committed

On Wed, 29 Sep 1999, Garrett Wollman wrote: > < said: > > > I believe this must be fixed. > > There is no way it can be ``fixed''. That's Just The Way It Is. I'm > sorry that you're having a problem with this. Nobody ever said > keeping -current would be easy. I have to agree with Rod that w

how to avoid bullets in the feet (was Re: HEADS UP: sigset_t changescommitted)

What's really needed is some warning sort of like what we did when the AOUT->ELF convertion happened, there has to be a simple way to test this as part of installworld. -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Wintelcom systems administrator and programmer - http://www.wintel

Re: HEADS UP: sigset_t changes committed

On Thu, Sep 30, 1999 at 01:29:40AM +1000, Marcel Moolenaar wrote: >Before attempting to build world, you must make and install a new >kernel. The new kernel will contain new syscalls that are needed during >build world. doscmd is currently not being build because it needs fixing >first. I'd like

Re: HEADS UP: sigset_t changes committed

I got world built and installed OK on the alpha now, and things generally seem OK. However, amd dumped core with a SEGV immediately upon startup. I haven't had even a second to try to debug it yet. Just thought I'd let you know about it. John -- John Polstra

Re: HEADS UP: sigset_t changes committed

On Thu, Sep 30, 1999 at 08:17:16AM +1000, Adam Strohl wrote: >On Wed, 29 Sep 1999, Jim Bloom wrote: > >>I believe this must be fixed. At some point in time, there is going >>to be another change to the kernel such that some older version of the >>code cannot run on a new kernel. > >FTPing a GENER

Re: HEADS UP: sigset_t changes committed

On Wed, 29 Sep 1999, Jim Bloom wrote: > I believe this must be fixed. At some point in time, there is going to be > another change to the kernel such that some older version of the code cannot run > on a new kernel. I believe this situation has occurred before. This will lead > to a situation

Re: HEADS UP: sigset_t changes committed

< said: > If it is broken, please back out the signal changes or fix the tools > target. No, Rod, just Deal With It(tm). -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

www.curriculum.com.br faz 6 meses de muito sucesso !

Esta contente com seu emprego atual? Já imaginou que poderia neste instante estar sendo chamado para uma entrevista em uma grande empresa, algo que poderia estar mudando completamente o seu futuro? Porque se privar desta possível oportunidade? Saia do anonimato! Independente se está ou não

Re: Is the wb driver broken?

Bill Paul wrote: > > You know, I have a rule about not doing software upgrades on > equipment that I can't actually get my hands on. Me too. That's why it's stressing me out. :-) I do have access to the serial console, and there are people on-site who can give the box a kick if I need them to.

Re: Is the wb driver broken?

Bill Paul wrote: > > I converted the wb driver to miibus ages ago. Your description makes > it sound like the problem just magically appeared yesterday. That's > a no-no, m'kay? Thanks for the quick reply. I didn't mean to imply anything. I have one machine with a Winbond running current a wee

Re: Is the wb driver broken?

Bill Paul wrote: >> >> OK, I did that and it made the SIOCSIFMEDIA message go away. But >> now it's not showing carrier: >> >> Doing initial network setup: hostname domain. >> wb0: flags=8843 mtu 1500 >> inet 204.216.27.25 netmask 0xfff0 broadcast 204.216.27.31 >> ether 00:0

Re: HEADS UP: sigset_t changes committed

Ben Rosengart writes: > On Wed, 29 Sep 1999, Harold Gutch wrote: > > > I interpreted the way of currently handling things (build the > > kernel first, then the userland) to be a _temporary_ solution, > > that Marcel was working on being fixed. If this is not the case, > > then I agree with

Re: Is the wb driver broken?

Of all the gin joints in all the towns in all the world, John Polstra had to walk into mine and say: > >> cvsup-master# ifconfig wb0 inet 204.216.27.25 netmask 255.255.255.240 > >> media 100baseTX mediaopt half-duplex > >> ifconfig: SIOCSIFMEDIA: Device not configured > > > > You don't need

Re: FICL breakage...

< said: > On Wed, Sep 29, 1999 at 04:17:50PM -0600, Warner Losh wrote: >> FWIW, one mus have perl installed to build a kernel. > Is that desirable? Or do we need more awk? Um, yes. The reason we have Perl in the base system is so that programs like this can be written -- in a way that (a) does

Is the wb driver broken?

I've run into a problem with the wb0 interface (Winbond) on a machine running -current from yesterday. (That's before any of the segset_t changes went in.) Unfortunately, the machine is cvsup-master.freebsd.org, which makes this pretty urgent. When I try to ifconfig the device, I get "ifconfig:

Re: HEADS UP: sigset_t changes committed

< said: > If I understand correctly, it only needs to be done once per system, but > it makes no difference whether it happens on a given system now or six > months from now. Surely. The thing we have to be careful about is making sure that the kernel does not grow new dependencies on software

Re: HEADS UP: sigset_t changes committed

I believe this must be fixed. At some point in time, there is going to be another change to the kernel such that some older version of the code cannot run on a new kernel. I believe this situation has occurred before. This will lead to a situation where a new kernel is required before the build

Re: Is the wb driver broken?

Of all the gin joints in all the towns in all the world, John Polstra had to walk into mine and say: > I've run into a problem with the wb0 interface (Winbond) on a > machine running -current from yesterday. (That's before any of > the segset_t changes went in.) Unfortunately, the machine is >

Re: HEADS UP: sigset_t changes committed

< said: > I believe this must be fixed. There is no way it can be ``fixed''. That's Just The Way It Is. I'm sorry that you're having a problem with this. Nobody ever said keeping -current would be easy. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the

Re: HEADS UP: sigset_t changes committed

> > Before attempting to build world, you must make and install a new > > kernel. The new kernel will contain new syscalls that are needed during > > build world. doscmd is currently not being build because it needs fixing > > first. > > Is there any way at all that we can change this proce

Re: Is the wb driver broken?

Of all the gin joints in all the towns in all the world, John Polstra had to walk into mine and say: > > Is there any reason why you're not letting it autodetect (which is > > what it does by default, or with media autoselect). > > I inherited an /etc/rc.conf file that somebody else set up. I'

Re: HEADS UP: sigset_t changes committed

On Thu, 30 Sep 1999, Harold Gutch wrote: > Uhm, that's the way I see it being _right now_ as well. What I > was thinking of, was that things would go smoother if you > wouldn't upgrade _right now_, but in [insert some time in the > near future here], as things would perhaps be "fixed" by then.

Re: HEADS UP: sigset_t changes committed

On Wed, 29 Sep 1999, Ben Rosengart wrote: > On Wed, 29 Sep 1999, Harold Gutch wrote: > > > I interpreted the way of currently handling things (build the > > kernel first, then the userland) to be a _temporary_ solution, > > that Marcel was working on being fixed. If this is not the case, > > the

Re: HEADS UP: sigset_t changes committed

> On Thu, 30 Sep 1999, Harold Gutch wrote: > > > Uhm, that's the way I see it being _right now_ as well. What I > > was thinking of, was that things would go smoother if you > > wouldn't upgrade _right now_, but in [insert some time in the > > near future here], as things would perhaps be "fixed"

Re: HEADS UP: sigset_t changes committed

On Wed, Sep 29, 1999 at 04:17:29PM -0700, Doug wrote: > On Wed, 29 Sep 1999, Ben Rosengart wrote: > > > On Wed, 29 Sep 1999, Harold Gutch wrote: > > > > > I interpreted the way of currently handling things (build the > > > kernel first, then the userland) to be a _temporary_ solution, > > > that

Re: FICL breakage...

On Wed, Sep 29, 1999 at 04:17:50PM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes: > : OTOH, if we are still perl-safe, I could send you the newer perl > : script, so you can adapt from that. > > FWIW, one mus have perl installed to build a kernel. Is that d

Re: HEADS UP: sigset_t changes committed

On Wed, 29 Sep 1999, Harold Gutch wrote: > I interpreted the way of currently handling things (build the > kernel first, then the userland) to be a _temporary_ solution, > that Marcel was working on being fixed. If this is not the case, > then I agree with you. If I understand correctly, it only

Re: Loss of Functionality with newpnp

In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes: : Let me chime in here. We *DO* care about ancient AIC drivers as long : as no PCMCIA alternative exists. Justin has said that porting old scsi aic to cam wouldn't be too hard, but would still provide a level of buginess that is too high..

Re: FICL breakage...

In message <[EMAIL PROTECTED]> Joe Abley writes: : > FWIW, one mus have perl installed to build a kernel. : : Is that desirable? Or do we need more awk? It simply is. It would be very hard, imho, to replace doug's perl scripts with awk ones. However, my knowledge of perl >> awk, so there maybe

Re: FICL breakage...

In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes: : OTOH, if we are still perl-safe, I could send you the newer perl : script, so you can adapt from that. FWIW, one mus have perl installed to build a kernel. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebs

Re: HEADS UP: sigset_t changes committed

On Wed, Sep 29, 1999 at 02:04:27PM -0700, Doug wrote: > On Wed, 29 Sep 1999, Harold Gutch wrote: > > > On Wed, Sep 29, 1999 at 11:55:23AM -0700, Doug wrote: > > > On Wed, 29 Sep 1999, Marcel Moolenaar wrote: > > > > > > > I just finished committing the sigset_t changes I worked on for the last >

Re: HEADS UP: sigset_t changes committed

In article <[EMAIL PROTECTED]>, Wilko Bulte <[EMAIL PROTECTED]> wrote: > As John Polstra wrote ... > > > > ===> usr.bin > > "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop > > "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop > > "/a/src/usr.bi

Re: HEADS UP: sigset_t changes committed

On Wed, 29 Sep 1999, Harold Gutch wrote: > On Wed, Sep 29, 1999 at 11:55:23AM -0700, Doug wrote: > > On Wed, 29 Sep 1999, Marcel Moolenaar wrote: > > > > > I just finished committing the sigset_t changes I worked on for the last > > > 5 weeks. > > > > > > Before attempting to build world, you m

Weird sockname errors with -current and apache

Greetings, I'm using -current on some web server/CGI processing machines. Yes I know all about using -current on production stuff, but we need the NFS, et al fixes due to the heavy NFS client activity on these systems, and I'm willing to take the good with the bad. I cvsup'ed and built wo

Re: HEADS UP: sigset_t changes committed

As John Polstra wrote ... > In article <[EMAIL PROTECTED]>, Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > > > > Alpha users are invited to test the changes since I've not been able to > > do that myself. I've done all I possibly could do to make this a > > success. > > It looks like real bad ne

Re: HEADS UP: sigset_t changes committed

On Wed, Sep 29, 1999 at 11:55:23AM -0700, Doug wrote: > On Wed, 29 Sep 1999, Marcel Moolenaar wrote: > > > I just finished committing the sigset_t changes I worked on for the last > > 5 weeks. > > > > Before attempting to build world, you must make and install a new > > kernel. The new kernel wi

Re: my repository is broken (more)

On Wed, Sep 29, 1999 at 04:58:34PM +, Bob Bishop wrote: > Hi, > > I wrote: > > ===> usr.sbin/lpr/filters.ru > > ===> usr.sbin/lpr/filters.ru/koi2alt > > make: don't know how to make koi2alt.c. Stop > > > >Apparently because... > > > > ache1999/09/22 19:54:45 PDT > > >

Re: HEADS UP: sigset_t changes committed

> Nate Williams wrote: > >> Following up on my previous mail regarding the panic on the Alpha, > >> I've been looking at the diff for the code in question, in > >> "src/sys/nfs/nfs_socket.c": > >> > >> @@ -1501,14 +1502,16 @@ > >> struct nfsreq *rep; > >> register struct proc *p;

Re: HEADS UP: sigset_t changes committed

Marcel Moolenaar wrote: > > Ok, this should do it. If it looks good to you, I'll commit this... Yes, it looks fine to me. You may not be able to commit it right away, though. It looks like freefall is down. Maybe they're putting in the new disk. I'll try the patch a little bit later today, a

Re: HEADS UP: sigset_t changes committed

John Polstra wrote: > > Following up on my previous mail regarding the panic on the Alpha, > I've been looking at the diff for the code in question, in > "src/sys/nfs/nfs_socket.c": > > @@ -1501,14 +1502,16 @@ > struct nfsreq *rep; > register struct proc *p; > { > + sigset

Re: HEADS UP: sigset_t changes committed

Doug wrote: > > On Wed, 29 Sep 1999, Marcel Moolenaar wrote: > > Is there any way at all that we can change this process so that > building the kernel first is not required? IIRC, you can use -DNOTOOLS. In that case the current tools are assumed to be sufficient for building world. But,

Re: HEADS UP: sigset_t changes committed

> Following up on my previous mail regarding the panic on the Alpha, > I've been looking at the diff for the code in question, in > "src/sys/nfs/nfs_socket.c": > > @@ -1501,14 +1502,16 @@ > struct nfsreq *rep; > register struct proc *p; > { > + sigset_t tmpset; > > +

Re: HEADS UP: sigset_t changes committed

Marcel Moolenaar wrote: > > Ok, this should do it. If it looks good to you, I'll commit this... I'm running it now, and so far it seems to have solved the problem. Could you also please get rid of that "# doscmd \" line from usr.bin/Makefile? Thanks, John To Unsubscribe: send mail to [EMAIL

Re: HEADS UP: sigset_t changes committed

Nate Williams wrote: >> Following up on my previous mail regarding the panic on the Alpha, >> I've been looking at the diff for the code in question, in >> "src/sys/nfs/nfs_socket.c": >> >> @@ -1501,14 +1502,16 @@ >> struct nfsreq *rep; >> register struct proc *p; >> { >> +

Re: HEADS UP: sigset_t changes committed

Following up on my previous mail regarding the panic on the Alpha, I've been looking at the diff for the code in question, in "src/sys/nfs/nfs_socket.c": @@ -1501,14 +1502,16 @@ struct nfsreq *rep; register struct proc *p; { + sigset_t tmpset; + tmpset = p->p_siglis

Re: HEADS UP: sigset_t changes committed

Marcel Moolenaar wrote: > John Polstra wrote: >> strip >> # doscmd \ >> .endif > > It doesn't give me any problems... Weird! It doesn't seem like the Alpha make should be different. >> I haven't found the bottom of the stack yet (11000 frames and >> counting ...). Le

Re: HEADS UP: sigset_t changes committed

John Polstra wrote: > > Marcel Moolenaar wrote: > > John Polstra wrote: > >> strip > >> # doscmd \ > >> .endif > > > > It doesn't give me any problems... > > Weird! It doesn't seem like the Alpha make should be different. As a first "guess": Either sendsig/sigreturn o

Re: HEADS UP: sigset_t changes committed

John Polstra wrote: > > I suspect it's caused by the trailing backslash in the "doscmd" line > near the end: > > strip > # doscmd \ > .endif It doesn't give me any problems... > Anyway, when the make buildworld failed, I tried to do a "cvs > status" or some such thing

Re: HEADS UP: sigset_t changes committed

On Wed, 29 Sep 1999, Marcel Moolenaar wrote: > I just finished committing the sigset_t changes I worked on for the last > 5 weeks. > > Before attempting to build world, you must make and install a new > kernel. The new kernel will contain new syscalls that are needed during > build world. doscmd

Re: HEADS UP: sigset_t changes committed

In article <[EMAIL PROTECTED]>, Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > > Alpha users are invited to test the changes since I've not been able to > do that myself. I've done all I possibly could do to make this a > success. It looks like real bad news for the Alpha. :-( I built and insta

Re: HEADS UP: sigset_t changes committed

Marcel Moolenaar wrote: > > These libraries either a) have one of the modified structures > visible in the interface, or b) use sigset_t internally and > may cause breakage if new binaries are used against libraries > that don't have the sigset_t change. This not an immediate > issue, but will be

Re: Repeatable panic in current, cause Netscape

On Wed, Sep 29, 1999 at 07:42:50PM +0200, Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > > The latest -current system crashes while starting up Netscape, mine > > version is 4.61, Linux one. It's fully repeatable in my case. I got > > crash dump and here's my dmesg and gdb trace: > > Make sure th

Re: ep0 etherlink III breakage

>> Mark Hittinger wrote: >> Hey per request I'm reporting some ep0 breakage in today's -current. I have >> an etherlink III 3c509B and the probing appears correct. >> Sequence of events boot -s >> # ifconfig ep0 inet 192.168.18.200 >> (PC hangs) >> Mor

Re: Repeatable panic in current, cause Netscape

Vallo Kallaste wrote: > The latest -current system crashes while starting up Netscape, mine > version is 4.61, Linux one. It's fully repeatable in my case. I got > crash dump and here's my dmesg and gdb trace: Make sure that the linux module is as uptodate as the kernel is. As a rule of thumb: r

warning: new signal snafu

Current users, Here's an addendum to Marcel's HEADS-UP about the new signal code. Marcel stated you need to build and install a new kernel prior to doing a make world. You also need to be careful about loading the old linux module when you reboot because you may have a panic. This may apply to

Re: my repository is broken (more)

In article , Bob Bishop <[EMAIL PROTECTED]> wrote: > I now suspect that cvsup.uk.freebsd.org isn't up-to-date. Anyone > know anything? Yes, I heard from the maintainer that its updates had been failing for a few days due to a configuration error. I believe

Re: ep0 etherlink III breakage

Mark Hittinger wrote: > Hey per request I'm reporting some ep0 breakage in today's -current. I have > an etherlink III 3c509B and the probing appears correct. > > Sequence of events boot -s > # ifconfig ep0 inet 192.168.18.200 > (PC hangs) > > More lat

Re: Repeatable panic in current, cause Netscape

On Wed, Sep 29, 1999 at 09:51:49AM -0700, Alfred Perlstein <[EMAIL PROTECTED]> wrote: > excellent, using kgbd, can you please type "up" until you hit > frame 5 and print the value of the ndp and some of the other > variables? A listing of the code at that location would also > be great. ('list'

my repository is broken (more)

Hi, I wrote: > ===> usr.sbin/lpr/filters.ru > ===> usr.sbin/lpr/filters.ru/koi2alt > make: don't know how to make koi2alt.c. Stop > >Apparently because... > > ache1999/09/22 19:54:45 PDT > > Removed files: > usr.sbin/lpr/filters.ru koi2alt.c >

Re: HEADS UP: sigset_t changes committed

> I just finished committing the sigset_t changes I worked on for the last > 5 weeks. Thanks Marcel, this was great, and the commit messages were outstanding (as well as humorous :). Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the mes

Re: Repeatable panic in current, cause Netscape

On Wed, 29 Sep 1999, Vallo Kallaste wrote: > Hello > > The latest -current system crashes while starting up Netscape, mine > version is 4.61, Linux one. It's fully repeatable in my case. I got > crash dump and here's my dmesg and gdb trace: > > Copyright (c) 1992-1999 The FreeBSD Project. >

HEADS UP: sigset_t changes committed

I just finished committing the sigset_t changes I worked on for the last 5 weeks. Before attempting to build world, you must make and install a new kernel. The new kernel will contain new syscalls that are needed during build world. doscmd is currently not being build because it needs fixing firs

Re: just found this

In message <[EMAIL PROTECTED]> Ville-Pertti Keinonen writes: : It isn't in -current, does this mean that it wasn't considered an : acceptable long-term solution? It wasn't a problem in -current due to a different way that things were done there. : Really large numbers of hardlinks are probably r

my repository is broken

Hi, ===> usr.sbin/lpr/filters.ru ===> usr.sbin/lpr/filters.ru/koi2alt make: don't know how to make koi2alt.c. Stop Apparently because... ache1999/09/22 19:54:45 PDT Removed files: usr.sbin/lpr/filters.ru koi2alt.c Log:

Re: FICL breakage...

Mark Murray wrote: > > Hi > > There is breakage in the new FICL. This fixes it... > > diff -u -d -r1.2 softcore.awk > --- softcore.awk1999/01/22 23:52:57 1.2 > +++ softcore.awk1999/09/29 09:47:30 > @@ -91,6 +91,6 @@ >printf "\"quit \";\n"; >printf "\n\nvoid ficlC

Re: FICL breakage...

Joe Abley wrote: > > I don't believe I ever got around to doing it at the time, but I'd > be more than happy to implement the changes now if (a) someone could > remind me what the compression logic should be, and (b) someone could > confirm that these changes haven't already been made :) AFAIK,

Re: FICL breakage...

On Wed, Sep 29, 1999 at 12:02:09PM +0200, Mark Murray wrote: > There is breakage in the new FICL. This fixes it... > > [awk diff] I remember a long time ago someone asked me to make some modifications to softcore.awk to compress the textual ficl keywords by eliminating double-spaces and newlines

Re: Loss of Functionality with newpnp

"Rodney W. Grimes" wrote: > > I also know that we are a lot better off with CAM, and could care less > that the old ancient AIC drivers are dead, but some how I am also pretty Let me chime in here. We *DO* care about ancient AIC drivers as long as no PCMCIA alternative exists. > sure we won't b

Re: C++ compiler not working in yesterdays current.

On Wed, 29 Sep 1999, Martin Nilsson wrote: > mysql-3.23.3 cc1plus reports out of swap space and exits when > compiling sql_yacc.cc add mode swap space using swapfile parameter in /etc/rc.conf or manually, with vnconfig/swapon commands. mysql will normally compile. sincerely, ilya naumov (at

FICL breakage...

Hi There is breakage in the new FICL. This fixes it... diff -u -d -r1.2 softcore.awk --- softcore.awk1999/01/22 23:52:57 1.2 +++ softcore.awk1999/09/29 09:47:30 @@ -91,6 +91,6 @@ printf "\"quit \";\n"; printf "\n\nvoid ficlCompileSoftCore(FICL_VM *pVM)\n"; printf

Repeatable panic in current, cause Netscape

Hello The latest -current system crashes while starting up Netscape, mine version is 4.61, Linux one. It's fully repeatable in my case. I got crash dump and here's my dmesg and gdb trace: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents

C++ compiler not working in yesterdays current.

I'm having problem compiling programs with the c++ compiler in current as of yesterday. kdelibs-1.1.2 fails in configure, cc1plus coredumps when trying to compile a STL test. mysql-3.23.3 cc1plus reports out of swap space and exits when compiling sql_yacc.cc Have anybody else experienced thi

Re: ESS1869 logical ID

On 29 Sep 1999, John Saunders wrote: > > > > unknown0: on isa0 > > pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 > > unknown1: at port 0x201 on isa0 > > unknown2: at port 0x168-0x16f,0x36e-0x36f >irq 9 on isa0 > > > > Interestingly, that last device "unkn

Re: just found this

Warner Losh <[EMAIL PROTECTED]> writes: > In message <[EMAIL PROTECTED]> Kenneth >Culver writes: > : Check this out, if anyone is intrested. > : > : I found this on packetstorm.securify.com tonight. Any ideas?? > Mycroft sent this out after we had fixed this before the 3.3R > release. At lea

Re: System crash on "vinum start"

On Monday, 27 September 1999 at 13:05:35 -0400, Brad Chisholm wrote: >>> I'm having a problem where the "vinum start" command crashes my system. >>> This happens regardless of whether it's being issued during bootup via >>> /etc/rc or from the command line on a running system. >>> >>> Interestingl