Re: Anticipated release date for 3.4

1999-01-16 Thread Jeffrey J. Mountin
At 12:25 PM 11/18/99 +0100, Sascha Blank wrote: >On Wed, Nov 17, 1999 at 02:54:05PM -0600, Jeffrey J. Mountin wrote: >> What happened to every 4 months? > >I wonder too. Is it really such a good idea to shorten the release >cycle even more so that we will have four releases a year now? I don't >

Re: Userconfig still not saving selections in 3.3R

1999-01-16 Thread Daniel C. Sobral
Robert Withrow wrote: > > Since we are slushing towards 3.4R: Apparently the "userconfig > not saving selections" bug reported in 3.1 is still apparent > in 3.3R. Is there an easy fix that could find itself into 3.4R? > > (I asked about this in questions and got a reply from someone who > vefif

Re: Anticipated release date for 3.4

1999-01-16 Thread Jeffrey J. Mountin
At 02:42 PM 11/18/99 -0800, Jordan K. Hubbard wrote: >> My psychic powers are telling me that this information will find it's >> way on to the front page of Slashdot in the near future. > >Heh. Wow, I wonder how he does it folks! :) "Believe them. They're for real" - late night psyhic ads >> A

Making local devices: /dev/MAKEDEV.local or something else?

1999-01-16 Thread William R. Somsky
With the talk of a 3.4-release starting to take shape, I figured it would be time to put forth an idea/question/thought that's been stirring about the back of my mind: Doing a "sh MAKEDEV all" builds all the standard and default devices for a system, but there are usually other that are needed f

Re: Anticipated release date for 3.4

1999-01-16 Thread Mike Harding
Did you read the isc release about what the latest patches fix? Pretty scary... Cc: "Jordan K. Hubbard" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Date: Thu, 18 Nov 1999 15:09:11 -0800 From: "Jordan K. Hubbard" <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] X-Loop: FreeBSD.ORG Prece

Re: Anticipated release date for 3.4

1999-01-16 Thread Mike Tancsa
At 05:42 PM 11/18/99 , Jordan K. Hubbard wrote: >netgraph, um, lots of fixes... um... anybody else remember what the >hell we added since 3.3? :-) Has PR 14614 ever been addressed (the mmap DoS) ? Someone alluded to a fix in current that would be back ported. --Mike