Re: "Safe" to go to -CURRENT
On Fri, 7 Jun 2002, Sheldon Hearn wrote: > > > On Thu, 06 Jun 2002 10:14:52 MST, "David O'Brien" wrote: > > > > There are still issues with the C++ compiler in the base system that > > > make building X and some other C++ ports tricky. > > > > There is no issue with the C++ compiler. There is issue with the X > > source that uses depreciated features. > > The fact remains, desktop-environment users looking for an easy ride should > not be jumping on the -CURRENT wagon bus just now. Such people probably > don't really care "whose fault it is". > Too late for me, I was very happy with my FreeBSD-4.5 I think that it is not safe to go to CURRENT, but If you use it for testing purposes, then "good luck" :) > But thanks for clarifying. I'll be sure to explain more carefully to > the next person who asks me whether now's a good time for -CURRENT. :-) > > Ciao, > Sheldon. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "Safe" to go to -CURRENT?
On Thu, 06 Jun 2002 10:14:52 MST, "David O'Brien" wrote: > > There are still issues with the C++ compiler in the base system that > > make building X and some other C++ ports tricky. > > There is no issue with the C++ compiler. There is issue with the X > source that uses depreciated features. The fact remains, desktop-environment users looking for an easy ride should not be jumping on the -CURRENT wagon bus just now. Such people probably don't really care "whose fault it is". But thanks for clarifying. I'll be sure to explain more carefully to the next person who asks me whether now's a good time for -CURRENT. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "Safe" to go to -CURRENT?
On Wed, Jun 05, 2002 at 08:46:59AM +, Christopher Nehren wrote: > I've been monitoring the -CURRENT mailing list for about a day or two, > and haven't seen anything that's really broken (except for GCC 3.x, > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > TIA for the info, You use C to rebuild your system -- so I would say you _do_ use(will) use GCC 3.x. The C compiler has been fine since day 1. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "Safe" to go to -CURRENT?
On Thu, Jun 06, 2002 at 10:54:15AM +0200, Sheldon Hearn wrote: > > I've been monitoring the -CURRENT mailing list for about a day or two, > > and haven't seen anything that's really broken (except for GCC 3.x, > > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > > TIA for the info, > > Chris > > There are still issues with the C++ compiler in the base system that > make building X and some other C++ ports tricky. There is no issue with the C++ compiler. There is issue with the X source that uses depreciated features. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "Safe" to go to -CURRENT?
÷ Thu, 06.06.2002, × 12:54, Sheldon Hearn ÎÁÐÉÓÁÌ: > > I've been monitoring the -CURRENT mailing list for about a day or two, > > and haven't seen anything that's really broken (except for GCC 3.x, > > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > > TIA for the info, > > Chris > > There are still issues with the C++ compiler in the base system that > make building X and some other C++ ports tricky. If you use a lot of X > applications, you might want to hold back if you're looking for a smooth > ride. > > The base system itself seems pretty stable, though. Not sure, yesterdays kernel give me panic somewhere about ufsdir. Week-old kernel work very good. Turning off softupdates and doing fsck not in background not helps. I will fill PR just after connecting serial console. > Ciao, > Sheldon. -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "Safe" to go to -CURRENT?
On 05 Jun 2002 08:46:59 GMT, Christopher Nehren wrote: > I've been monitoring the -CURRENT mailing list for about a day or two, > and haven't seen anything that's really broken (except for GCC 3.x, > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > TIA for the info, > Chris There are still issues with the C++ compiler in the base system that make building X and some other C++ ports tricky. If you use a lot of X applications, you might want to hold back if you're looking for a smooth ride. The base system itself seems pretty stable, though. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "Safe" to go to -CURRENT?
On Wed, Jun 05, 2002 at 08:46:59AM +, Christopher Nehren wrote: > I've been monitoring the -CURRENT mailing list for about a day or two, > and haven't seen anything that's really broken (except for GCC 3.x, > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > TIA for the info, What do you do with the system? It is fairly difficult to make any recommendation without some info about what the system does. For example, is this a production box? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
